From: Andreas Schwab <schwab@suse.de>
To: Phil Edwards <phil@jaj.com>
Cc: Alexandre Oliva <aoliva@redhat.com>, Tom Womack <tom@womack.net>,
gcc@gcc.gnu.org, Mike Stump <mrs@windriver.com>
Subject: Re: Several snapshots on the same system?
Date: Sun, 10 Feb 2002 08:19:00 -0000 [thread overview]
Message-ID: <je3d09pbcb.fsf@suse.de> (raw)
In-Reply-To: <20020209235857.A28765@disaster.basement.lan> (Phil Edwards's message of "Sat, 9 Feb 2002 23:58:57 -0500")
Phil Edwards <phil@jaj.com> writes:
|> On Sun, Feb 10, 2002 at 12:21:49AM -0200, Alexandre Oliva wrote:
|> > I'm not sure the GCC docs are the proper place to teach about all
|> > sorts of caveats of Unix shells. The original Bourne shell does not
|> > even handle ~ especially, and other shells such as ksh and bash only
|> > handle ~ especially when it appears unquoted in the beginning of a
|> > command-line argument.
|>
|> Recent versions of bash (I don't know what the minimum version number is)
|> only require the tilde to appear at the beginning of something that could
|> be a path, e.g.,
|>
|> --prefix=/this/is/a/~weird/patch
|>
|> the tilde will not be expanded, but in
|>
|> --prefix=~/install
|>
|> it will be.
No, it won't. The expansion only occurs as part of an assignment.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-02-10 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 6:29 Tom Womack
2002-02-09 18:24 ` Alexandre Oliva
2002-02-10 3:21 ` Phil Edwards
2002-02-10 8:19 ` Andreas Schwab [this message]
2002-02-11 11:33 ` Phil Edwards
2002-02-12 8:54 ` Tom Womack
-- strict thread matches above, loose matches on Subject: below --
2002-02-06 12:13 mike stump
2002-02-07 6:24 ` Tom Womack
2002-02-06 1:55 Tom Womack
2002-02-06 3:16 ` Andreas Jaeger
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=je3d09pbcb.fsf@suse.de \
--to=schwab@suse.de \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mrs@windriver.com \
--cc=phil@jaj.com \
--cc=tom@womack.net \
/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).