bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tilde expansion during command search


From: Dan Douglas
Subject: Re: Tilde expansion during command search
Date: Thu, 24 Jul 2014 15:20:32 -0500
User-agent: KMail/4.13.3 (Linux/3.16.0-rc6; KDE/4.13.3; x86_64; ; )

On Thursday, July 24, 2014 02:34:13 PM lolilolicon wrote:
> On Wed, Jul 23, 2014 at 11:00 PM, lolilolicon <address@hidden> wrote:
> > On Wed, Jul 23, 2014 at 10:43 PM, Eric Blake <address@hidden> wrote:
> >> But we are talking about the case where ~ IS quoted during
> >> the assignment, and only bash then re-expands it during path lookup.
> >
> > That's my point. Let me try quoting this again,
> >
> >     Note that the tildes are expanded during the assignment to PATH, _not
> >     when PATH is accessed during command search._
> >
> > in which I was trying to imply that, Bash *does* expand the tildes _when
> > PATH is accessed during command search._
> 
> I'm sorry if it felt like I was taking that sentence out of context.
> Well, I was; but I think it's fair to assume that whoever wrote that
> sentence would agree that tilde expansion should not be performed when
> PATH is accessed during command search.

The section you quoted isn't present at all in issue 7. The current version of 
the spec makes tilde expansion within assignments mandatory, including 
multiple tilde expansions when there are colons. The part that describes how 
that works moved to XRAT section 2.6.1. However the part that refers to what 
happens during command search appears to have been removed.

I agree that if the quoted sentence were present it would probably imply that 
this behavior is explicitly disallowed.
-- 
Dan Douglas



reply via email to

[Prev in Thread] Current Thread [Next in Thread]