This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: bash shell question
- To: Michael Zawacki <mjz115 at psu dot edu>
- Subject: Re: bash shell question
- From: Tomas Fasth <tomas dot fasth at twinspot dot net>
- Date: Tue, 25 Nov 1997 14:57:51 +0100
- CC: "'gnu-win32 at cygnus dot com'" <gnu-win32 at cygnus dot com>
- Organization: EuroNetics Operation
- References: <01BCF866.352EE670@ppp81.cac.psu.edu>
Michael, you can fix your problem in at least two ways as I can see it.
One way is to quote the 'filename' variable expansion like this:
ln -s "$filename"
The shell is passing arguments after having them processed by the usual
whitespace rule. By adding quotes the shell will treat it as a single
argument. In this case you should not have any quotes in the execs.txt
file, otherwise the quotes will be regarded as part of the path name.
The other way is to keep your quotes in the execs.txt file and instead
evaluate the ln command line. Like this:
eval ln -s $filename
In this case, the shell is becoming aware of any quotes that exists in
the execs.txt file.
The result would be identical in both cases and should fix your problem.
Tomas
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".