From: Steve Dondley <s@dondley.com>
To: "Mark J. Reed" <markjreed@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Can't tell the difference in operation between PATH_SCRIPT and NO_PATH_SCRIPT
Date: Fri, 26 Jan 2024 12:21:39 -0500 [thread overview]
Message-ID: <ABFF80FF-080B-4FD0-8C08-120406E1EDBA@dondley.com> (raw)
In-Reply-To: <CAA=-s3xX1WUikhzWLw61=F4gtzZCqwC2tLCe0pgxy0jeiO3yRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
>
> This is why the documentation for the PATH_SCRIPT option in zshoptions(1) points you to the INVOCATION section of the main zsh manual: the option is really only useful when specified on the command line.
>
I’ve got lots of quibbles with how that section is written. It is not for mere mortals.Take just the first sentence, for example:
"The following flags are interpreted by the shell when invoked to determine where the shell will read commands from:"
“when invoked” is bad jargon. The use of passive voice is confusing and “to determine where the shell will read commands from” is just torturous wording.
Instead:
A user or script can use the appropriate command, usually /bin/zsh, to launch a new z shell process. Optional flags passed to the command control where the shell looks for new commands to interpret:
[-- Attachment #2: Type: text/html, Size: 1414 bytes --]
next prev parent reply other threads:[~2024-01-26 17:22 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 [this message]
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=ABFF80FF-080B-4FD0-8C08-120406E1EDBA@dondley.com \
--to=s@dondley.com \
--cc=markjreed@gmail.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).