From: Ray Andrews <rayandrews@eastlink.ca>
To: 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 11:42:55 -0800 [thread overview]
Message-ID: <395469e2-bcfe-467b-b749-85a284876b64@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMopH9F2iaaoDqmu1ROmAXRSrt-Pbb40NrnvOSXGvowhYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
On 2024-01-26 10:38, Roman Perepelitsa wrote:
> I respectfully disagree. In my experience, Unix man pages, in
> particular zsh documentation, are excellent resources, effectively
> tailored to their intended audience. I'm part of that demographic and
> find them incredibly useful.
They are indispencible in the same way that the blueprints of a nuclear
power station are indicpencible and if you are already an expert you may
find them even friendly. But if you aren't an expert the docs are cold
help becoming one. It's like trying to learn Hungarian by reading a
Hungarian grammar written in Hungarian from one Hungarian grammarian to
another.
> Difficulty in understanding content, like
> cooking recipes in my case, often stems from it not being designed for
> our specific knowledge base. This doesn't diminish the quality of the
> content itself.
Quality is not in question, rather presumed reader and specific goals.
Again, if you are already an expert the manual is your reference to
recall some detail or other and it could hardly be better. But if you
want to *understand* the shell, best to read Peter's book or some other
resource. The manual stores information but explains nothing. It is
also written in shell jargon which if fine if you already speak shell
jargon.
[-- Attachment #2: Type: text/html, Size: 1984 bytes --]
next prev parent reply other threads:[~2024-01-26 19:43 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 [this message]
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=395469e2-bcfe-467b-b749-85a284876b64@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).