[NSIS-Bugs] [ nsis-Bugs-1883917 ] File command reference not clear

[SourceForge.net <no...@so...>]

Bugs item #1883917, was opened at 2008-01-31 22:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=1883917&group_id=22049

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: 2.0 Series
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Message (message09)
Assigned to: Nobody/Anonymous (nobody)
Summary: File command reference not clear

Initial Comment:
I've found an incongruity in the command reference, the File command:

"If the /oname=X switch is used, the output name becomes $OUTDIR\X. When using the /oname= switch, only one file can be specified, and the file name can contain variables (or a fully qualified path, e.g. $SYSDIR\whatever.dll)."

According to this, if I put /oname=$SYSDIR\whatever.dll, the output name would become $OUTDIR\$SYSDIR\whatever.dll. While in reality it becomes plain $SYSDIR\whatever.dll.

Also the manual does not answer the following question: If I specify a non-existing directory in /oname, will the File command create it?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=1883917&group_id=22049