From: Chet Ramey <chet@odin.INS.CWRU.Edu>
To: eric@osiris.com.au
Cc: gnu-win32@cygnus.com
Subject: Re: bash env parse broken
Date: Thu, 04 Sep 1997 21:18:00 -0000 [thread overview]
Message-ID: <970904133102.AA26812.SM@odin.INS.CWRU.Edu> (raw)
In-Reply-To: <9709021133.AA20403@osiris.com.au>
> on NT4.0sp3 gnu-win32 B18 ... sourcing the following 12 lines into bash:
>
> HOMEPATH="\"
> export HOMEPATH
> UNAME="NT 4.0"
> export UNAME
> NEW_RELEASE="28/08/97"
> export NEW_RELEASE
> TCL_LIBRARY="C:/gnuwin32/b18/tcl/lib/tcl7.6"
> export TCL_LIBRARY
> PATH=".:/bin:/gnuwin32/b18/H-i386-cygwin32/bin:/gnuwin32/b18/tcl/bin:/WINNT/system32:/WINNT:/msdev/bin:/fax/dev:/fax/dev"
> export PATH
> GCC_EXEC_PREFIX="C:\gnuwin32\b18\H-i386-cygwin32\lib\gcc-lib\"
> export GCC_EXEC_PREFIX
You have an unmatched double quote. The assignment to HOMEPATH
doesn't end until the first double quote after the `UNAME='.
Backslashes quote double quotes inside double-quoted strings. I don't
know why bash throws an exception on cygwin32, but on Unix the error
messages are correct.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-09-04 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-02 15:50 Eric Mills
1997-09-04 12:06 ` Aaron P. Siri
1997-09-04 21:18 ` Chet Ramey [this message]
1997-09-08 19:18 Eric Mills
1997-09-09 0:16 ` Alex
1997-09-09 16:24 dahms
1997-09-09 23:33 dahms
1997-09-10 1:50 Bryan T. Schmersal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=970904133102.AA26812.SM@odin.INS.CWRU.Edu \
--to=chet@odin.ins.cwru.edu \
--cc=eric@osiris.com.au \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).