From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Steve Dondley" <s@dondley.com>
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:35:38 -0500 [thread overview]
Message-ID: <5b4c2f63-875d-4b8b-b8bc-dce2ed0b4ab6@app.fastmail.com> (raw)
In-Reply-To: <73E4333B-C282-4A58-837C-A50F73E13289@dondley.com>
On Thu, Jan 25, 2024, at 9:00 PM, Steve Dondley wrote:
> I’ve been looking over the documentation and I really can’t make sense
> out of what the PATH_SCRIPT option is supposed to do.
>
> If it’s set, which it is by default
This is not true. PATH_SCRIPT is only set by default in ksh/sh
emulation.
--
vq
prev parent reply other threads:[~2024-01-26 4:36 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
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 [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=5b4c2f63-875d-4b8b-b8bc-dce2ed0b4ab6@app.fastmail.com \
--to=larryv@zsh.org \
--cc=s@dondley.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).