From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: dash@vger.kernel.org
Subject: Re: % in $PATH
Date: Mon, 10 Nov 2014 23:15:24 +0000 [thread overview]
Message-ID: <20141110231524.GC3938@chaz.gmail.com> (raw)
In-Reply-To: <20141110223951.GB25437@hal.lan>
2014-11-10 23:39:51 +0100, Guido Berhoerster:
[...]
> That leaves the /path%func
> case but there is precendence with FPATH as a solution if "%" is
> to be completely eliminated from PATH.
[...]
Where ash's $PATH handling is superior to $FPATH is that you can
specify which fpath component has precedence over which path
component and over builtins.
My problem as reported is that the namespace reserved by ash
(any component with % in it) was too wide (and
unnecessarily so). If you make it any component ending in %func
or %builtin, that's far less of an issue (as long as it's
documented).
I won't shed a tear if that feature is removed. I'm just feeling
it's not necessary to remove it, it could just be made more
innocuous.
--
Stephane
prev parent reply other threads:[~2014-11-10 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 11:59 % in $PATH Stephane Chazelas
2014-11-10 13:20 ` Herbert Xu
2014-11-10 21:30 ` Stephane Chazelas
2014-11-10 21:59 ` Guido Berhoerster
2014-11-10 22:23 ` Stephane Chazelas
2014-11-10 22:39 ` Guido Berhoerster
2014-11-10 23:15 ` Stephane Chazelas [this message]
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=20141110231524.GC3938@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=dash@vger.kernel.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