From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Makefile bug.
Date: 16 May 2001 17:07:25 +0200 [thread overview]
Message-ID: <vafk83hbadu.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vxk7kzh5pxs.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "16 May 2001 10:27:59 -0400")
On 16 May 2001, Karl Kleinpaste wrote:
> [[ Quoting Chet Ramey: ]]
>
> Bash does tilde expansion in words that appear to be variable
> assignments (POSIX.2, section 3.6.1). POSIX says to do it only for
> assignment statements preceding a command, but bash does it for any
> word that looks like an assignment statement (unless bash is running
> in posix mode). Since the leading `--' makes an invalid lhs for a
> variable assignment, --prefix=~xxx is not a candidate for tilde
> expansion. However, `make DESTDIR=~/bin' would be tilde expanded,
> even though POSIX says not to.
IMVHO it would be useful for bash to tilde-expand `--prefix=~/foo'.
If I understand Chet correctly, bash has a posixly correct and a
normal mode -- how about tilde-expanding `--prefix=~/foo' in normal
mode (but to refrain from expanding in posixly correct mode)?
kai
--
The passive voice should never be used.
next prev parent reply other threads:[~2001-05-16 15:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 6:46 Gaute B Strokkenes
2001-05-16 9:41 ` Kai Großjohann
2001-05-16 9:51 ` Peter Makholm
2001-05-16 10:09 ` Gaute B Strokkenes
2001-05-16 10:50 ` Kai Großjohann
2001-05-16 12:32 ` Denys Duchier
2001-05-16 13:11 ` Kai Großjohann
2001-05-16 15:18 ` Denys Duchier
2001-05-16 14:20 ` Gaute B Strokkenes
2001-05-16 15:03 ` Kai Großjohann
2001-05-17 0:19 ` Gaute B Strokkenes
2001-05-17 8:45 ` Kai Großjohann
2001-05-16 12:38 ` Michael.Cook
2001-05-16 14:27 ` Karl Kleinpaste
2001-05-16 15:07 ` Kai Großjohann [this message]
2001-05-16 16:34 ` Alexandre Oliva
2001-05-17 0:21 ` Gaute B Strokkenes
2001-05-16 18:55 ` Raja R Harinath
2001-05-17 8:45 ` Kai Großjohann
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=vafk83hbadu.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).