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: Chet Ramey
Subject: Re: Tilde expansion during command search
Date: Fri, 01 Aug 2014 11:28:46 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/1/14, 11:26 AM, Eric Blake wrote:
> On 08/01/2014 07:53 AM, Dan Douglas wrote:
> 
>>> how so ?  execvp doesn't do tilde expansion.  only the shell does.
>>
>> That's the problem. A program using execvp should be able to expect the same 
>> result as that of the shell for a given PATH value. Because of this, it 
>> can't, unless exec has the same implementation.
>>
>>> and it does it once at assignment.
>>
>> The example from my first post demonstrates that Bash substitutes a literal 
>> tilde in PATH during the actual path search before executing a command, in 
>> addition to during assignments and word expansions.
> 
> And that bash is the odd one out in comparison to all other shells.  I
> think bash is buggy for performing tilde expansion during PATH lookup
> for literal tildes contained in PATH, because no other shell does it,
> and POSIX does not specify that it would happen.

Again: if it were a real problem, you'd think it would have come up more
often in the past 25 years since it was implemented.

- -- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlPbsi0ACgkQu1hp8GTqdKtKGwCZAa+2Js8aibplmc17DPEBtEYd
NQUAni/qbNXIQLiTQRfW052G9asC3lnY
=oOKU
-----END PGP SIGNATURE-----



reply via email to

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