[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: |
Wed, 23 Jul 2014 08:51:19 -0500 |
User-agent: |
KMail/4.13.3 (Linux/3.16.0-rc5; KDE/4.13.3; x86_64; ; ) |
On Wednesday, July 23, 2014 09:28:02 AM you wrote:
> On 7/23/14, 8:22 AM, Dan Douglas wrote:
> > Hi, from this discussion:
> >
> > https://github.com/koalaman/shellcheck/issues/195#issuecomment-49678200
> >
> > I can't find any reference that says substituting a literal tilde in PATH
> > should occur during command search.
>
> Bash has always done this, even back to the pre-version 1 days, and I don't
> see any reason to change it now.
>
The only concerns I can think of are inconsistency with programs that use
execvp(), or possibly double-expansion in the event of a user name or any path
containing ~.
You're probably right in that it's not super critical if it hasn't caused
problems so far.
--
Dan Douglas
- Tilde expansion during command search, Dan Douglas, 2014/07/23
- Re: Tilde expansion during command search, Chet Ramey, 2014/07/23
- Re: Tilde expansion during command search,
Dan Douglas <=
- Re: Tilde expansion during command search, Eric Blake, 2014/07/23
- Re: Tilde expansion during command search, Dan Douglas, 2014/07/23
- Re: Tilde expansion during command search, lolilolicon, 2014/07/23
- Re: Tilde expansion during command search, Eric Blake, 2014/07/23
- Re: Tilde expansion during command search, Eric Blake, 2014/07/23
- Re: Tilde expansion during command search, lolilolicon, 2014/07/23
- Re: Tilde expansion during command search, lolilolicon, 2014/07/24
- Re: Tilde expansion during command search, Dan Douglas, 2014/07/24