From: Steve Dondley <s@dondley.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: zsh-users@zsh.org
Subject: Re: Can't tell the difference in operation between PATH_SCRIPT and NO_PATH_SCRIPT
Date: Thu, 25 Jan 2024 23:17:20 -0500 [thread overview]
Message-ID: <3DC872AC-5B19-468D-85D5-5D3A501EF7E9@dondley.com> (raw)
In-Reply-To: <4a1df20e-70c4-41ed-b370-4fbbae0619b9@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
I guess I never realized that, when it comes to options, there is a difference between running a script directly and passing it as an argument to zsh.
But even still, If I do this:
> echo $PATH
/usr/bin:./dir
> ls dir
-rwxr--r-- 1 root root 9 Jan 26 03:26 foo.zsh
> setopt pathscript
> zsh foo.zsh
zsh: can't open input file: foo.zsh
> unsetopt pathscript
> zsh foo.zsh
zsh: can't open input file: foo.zsh
So I’m still seeing no difference between execution of the script with path script on or off in these cases.
HOWEVER, I discovered if I put this in my .zshrc:
setopt pathscript
and do:
> zsh -i foo.zsh
It works.
Or, if I do
> setopt pathscript
and then do
> zsh -c foo.zsh
This also works.
> zsh -i foo.zsh wil also work in this case, too.
> On Jan 25, 2024, at 10:45 PM, Lawrence Velázquez <larryv@zsh.org> wrote:
>
> On Thu, Jan 25, 2024, at 10:21 PM, Steve Dondley wrote:
>> Sorry, I’ve got a bad misconcepiton somewhere. I stil don’t get it.
>>
>> I do: PATH=.dir
>>
>> When I do: setopt pathscript
>> And then do: foo.zsh
>>
>> It finds foo in the ./dir directory and executes it.
>>
>>
>> Then when i do: unsetopt pathscript
>> And then I do: foo.zsh
>>
>> It stil finds foo.zsh in the ./dir directory.
>>
>> So I’m not seeing how it behaves any differently.
>
> You doing something completely different from what I described and
> demonstrated. PATH_SCRIPT *only* affects how zsh behaves when you
> invoke it to run a script (e.g., ''zsh script_name''). It does not
> affect PATH searches performed as part of command execution.
>
> --
> vq
[-- Attachment #2: Type: text/html, Size: 22647 bytes --]
next prev parent reply other threads:[~2024-01-26 4:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 2:00 Steve Dondley
2024-01-26 3:05 ` Lawrence Velázquez
2024-01-26 3:21 ` Steve Dondley
2024-01-26 3:30 ` Steve Dondley
2024-01-26 3:45 ` Lawrence Velázquez
2024-01-26 4:17 ` Steve Dondley [this message]
2024-01-26 4:58 ` Lawrence Velázquez
2024-01-26 5:20 ` Steve Dondley
2024-01-26 5:52 ` Bart Schaefer
2024-01-26 6:35 ` Lawrence Velázquez
2024-01-26 15:49 ` Steve Dondley
2024-01-26 16:07 ` Mark J. Reed
2024-01-26 16:41 ` Mark J. Reed
2024-01-26 17:21 ` Steve Dondley
2024-01-26 18:28 ` Ray Andrews
2024-01-26 18:38 ` Roman Perepelitsa
2024-01-26 19:17 ` Steve Dondley
2024-01-26 19:38 ` Roman Perepelitsa
2024-01-26 19:52 ` Steve Dondley
2024-01-26 20:06 ` Ray Andrews
2024-01-26 20:16 ` Lawrence Velázquez
2024-01-26 19:54 ` Ray Andrews
2024-01-26 20:05 ` Steve Dondley
2024-01-26 20:43 ` Steve Dondley
2024-01-27 2:34 ` .m0rph
2024-01-26 19:42 ` Ray Andrews
2024-01-26 20:08 ` Roman Perepelitsa
2024-01-26 20:21 ` Steve Dondley
2024-01-26 20:40 ` Ray Andrews
2024-01-26 6:25 ` Lawrence Velázquez
2024-01-26 6:42 ` Lawrence Velázquez
2024-01-26 15:27 ` Steve Dondley
2024-01-26 4:35 ` Lawrence Velázquez
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=3DC872AC-5B19-468D-85D5-5D3A501EF7E9@dondley.com \
--to=s@dondley.com \
--cc=larryv@zsh.org \
--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).