From: Ray Andrews <rayandrews@eastlink.ca>
To: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: PATH_DIRS
Date: Thu, 10 Aug 2017 22:07:27 -0700 [thread overview]
Message-ID: <1852003c-c07c-dc61-b863-007f0cef9111@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Yd0O2_KqXe84X95-zgLFZOoCzLPKMWUrkT6hGh4jf8Ww@mail.gmail.com>
On 10/08/17 03:19 PM, Bart Schaefer wrote:
> PATH_DIRS is a setopt, it *uses* $PATH. It's not a parameter
> providing alternate directories.
I would have been up the garden path there, cuz I:
$ PATH_DIR=/aWorking/Zsh/System
$ echo $PATH_DIR
/aWorking/Zsh/System
... which seemed to do just as I thought I was expecting, however now I
see that since that directory is on my PATH anyway, it worked but only
(it seems) by virtue of it working all the time anyway and I just
didn't realize that, and I was making an unrelated and useless variable
:( Now I see that I completely missed the real use of that setopt.
Thanks, God only knows how many knots I'd have tied myself into there.
>
> Anyway, it already does search like that. You just have to chmod +x
> the script files (and add a #! line if they aren't zsh scripts).
However, scripts are run even if chmod -x, tho whence will only find
them if '+x'. Am I somehow missing the boat there?
>
> What it WON'T do is source scripts it finds that way into the current
> shell. It'll always fork a subshell for them. Too many opportunities
> for mayhem if the user hasn't explicitly asked (via the "." command)
> to have his current shell altered (potentially) by the script.
>
Yeah, I don't begrudge the dot, good to know what one is doing. Still, I
find myself wanting whence to find anything that is executable on the
PATH. If I can:
/aWorking/Zsh/System $ ls -l somescript
-rw-r--r-- 1 root root 24 Aug 10 21:55 somescript <<< not marked
executable.
/aWorking/Zsh/System $ cat somescript
echo this is somescript
/aMisc $ . somescript
this is somescript
... so it will be run if it's a script on my PATH, even if not '+x' then
it seems intuitive that whence would also be able to find it.
next prev parent reply other threads:[~2017-08-11 5:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 21:46 PATH_DIRS Ray Andrews
2017-08-10 22:19 ` PATH_DIRS Bart Schaefer
2017-08-11 5:07 ` Ray Andrews [this message]
2017-08-11 16:12 ` PATH_DIRS Ray Andrews
2017-08-14 3:20 ` PATH_DIRS Bart Schaefer
2017-08-15 3:53 ` PATH_DIRS Ray Andrews
2017-08-15 16:50 ` PATH_DIRS Jim
2017-08-15 17:32 ` PATH_DIRS Bart Schaefer
2017-08-16 16:22 ` PATH_DIRS Ray Andrews
2017-08-20 10:59 ` PATH_DIRS Jim
2017-08-20 16:50 ` PATH_DIRS Ray Andrews
[not found] ` <CA+rB6GL7tv+_tyswyZYFLksy_+oQ4Nk8ZQ9FRDW8h1dfnKdUgw@mail.gmail.com>
2017-08-16 14:45 ` PATH_DIRS Ray Andrews
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=1852003c-c07c-dc61-b863-007f0cef9111@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).