zsh-users
 help / color / mirror / code / Atom feed
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 12:40:24 -0800	[thread overview]
Message-ID: <81b44e1d-49f4-48ab-99ed-4aaf2f20e8d7@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMpcTGiKB7F+nyPnqo7Rdfw7Ja=_V+W+PeGA8UWjes2Daw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]


On 2024-01-26 12:08, Roman Perepelitsa wrote:
> Exactly, zsh documentation is a nuclear power station blueprints.
> Transforming it into a basic physics tutorial

I quite agree.  A manual is not a tutorial.  Still, that's no reason for 
the manual to be impenetrable -- as if that was somehow a virtue.  A 
while back Peter rewrote something and it went from being baffling to 
being helpful.  Why *not* make things as clear as possible?


> I agree that your version would be better for someone unfamiliar withthis concept.But can you see that it might be less efficient for
> someone who already understands it? And consider where to draw the
> line with foundational explanations. Should we also explain what $HOME
> is, what a directory means, or what 'consult' implies?

It's always a matter of judgement where one draws the line.  It goes 
without saying that things should not be dumbed down to the point of 
dilution.  Within, say, a thousand words, why not make those thousand 
words as clear as they can be?  Steve's sample -- what is *lost*?  What 
utility is compromised?  If much is gained and nothing is lost, I say 
it's a plain improvement.  Put it this way: if my needs and your needs 
are in conflict as to the manual, yours must prevail.  But what if my 
needs could be met without compromising yours?



[-- Attachment #2: Type: text/html, Size: 2330 bytes --]

  parent reply	other threads:[~2024-01-26 20:40 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 [this message]
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=81b44e1d-49f4-48ab-99ed-4aaf2f20e8d7@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).