From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: dash@vger.kernel.org
Subject: % in $PATH
Date: Wed, 5 Nov 2014 11:59:47 +0000 [thread overview]
Message-ID: <20141105115946.GA4029@chaz.gmail.com> (raw)
Hello,
ash/dash have a nice feature that allows to have:
PATH=/bin:%builtin:/usr/bin:/some/dir%func:/sbin
To have commands in /bin take precedence over builtins and
files in /some/dir being looked up for autoloaded functions (a
bit like FPATH in ksh/zsh).
That's nice but the way it is implemented, that means that %
characters in $PATH cause problems. See for instance:
http://unix.stackexchange.com/questions/126955/percent-in-path-environment-variable
Where someone ran into it when they had a:
/home/torbjorr/deployed/vector/x86_64-GNU%2fLinux directory in
there.
Given than only "builtin" and "func" are recognised after "%", I
think it would be better if the PATH handling accepted any other
string like "foo%bar", "foo%2f", "foo%functions" as-is as a
normal $PATH component.
And foo%2fbar%func meaning "foo%2fbar" treated as a directory
with autoloadable functions.
--
Stephane
next reply other threads:[~2014-11-05 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 11:59 Stephane Chazelas [this message]
2014-11-10 13:20 ` % in $PATH 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
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=20141105115946.GA4029@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).