zsh-users
 help / color / mirror / code / Atom feed
From: Steve Dondley <s@dondley.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Ray Andrews <rayandrews@eastlink.ca>, 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 14:17:14 -0500	[thread overview]
Message-ID: <D343B968-5407-4449-A9F6-A09C26FB321E@dondley.com> (raw)
In-Reply-To: <CAN=4vMopH9F2iaaoDqmu1ROmAXRSrt-Pbb40NrnvOSXGvowhYQ@mail.gmail.com>

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

> 
> 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. 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.


Well, I like to talk about specific examples. Speaking in generalities about whether documentation is good/bad gets us nowhere.

So if you got to Chapter 5, paragraph 2, you’ll see:
It is also possible for a file in $ZDOTDIR to re-enable GLOBAL_RCS. Both RCS and GLOBAL_RCS are set by default.


Now, I’m not exactly a newb but I’m far from an expert. But I fell like I’m getting assaulted out of the blue with this before unmentioned $ZDOTDIR variable. Immediately my mind starts spinning with questions:

1) where is this variable set?
2) what are some typical values for it?
3) do I have to worry about this if I’m using the XDG config
4) does the OS handle this for me? 
5) This looks like an environment variable? Is it an environment variable or something different?

Yes, I'm getting technically accurate information about this variable. But nowhere does the documentation give me any clue on how to use this setting in a practical way and why it might be useful to me.

So next I search through the manual. I see ZDOTDIR listed in the “Parameters” chapter. I have no idea what a “Parameter” is. Is this an environment variable? And I don’t get any of my other questions answered. 

I could go on. But my main point is that it feels like the documentation makes the assumption you know how a typical shell works and that you are familiar with the many common features between the different kinds of shells. That’s fine, but it feels like the documenation could put in a much better effort of at least giving you a bit more of a big picture clue if you don’t have one.

Couple this problem with wording that is stylistically like nails on a chalkboard  and you are in for a very tough slog. You have to have a huge amount of time on your hands to get through it. 

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

  reply	other threads:[~2024-01-26 19:18 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 [this message]
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=D343B968-5407-4449-A9F6-A09C26FB321E@dondley.com \
    --to=s@dondley.com \
    --cc=rayandrews@eastlink.ca \
    --cc=roman.perepelitsa@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).