zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: manual
Date: Thu, 22 Dec 2022 06:20:58 -0800	[thread overview]
Message-ID: <ccb7c9a1-d8ae-de33-f2d1-20b10e1187e1@eastlink.ca> (raw)
In-Reply-To: <05989f02-59f4-49cf-b766-39fda9a5154a@app.fastmail.com>


On 2022-12-21 22:31, Lawrence Velázquez wrote:
>
> It already says where to look.
>
> 	For the meaning of the other flags, see zshoptions(1).

I know it.  They send you to another section entirely which is 1487 
lines long.  Not very friendly.  Please understand that it's my 'job' in 
a discussion like this to be crabby and snotty and hard to please.   
Devil's advocate is what I'm being.


> 	Some options also have one or more single letter names.
> 	There are two sets of single letter options: one used by
> 	default, and another used to emulate sh/ksh (used when the
> 	SH_OPTION_LETTERS option is set).  The single letter options
> 	can be used on the shell command line, or with the `set',
> 	`setopt' and `unsetopt' builtins, as normal Unix options preceded
> 	by `-'.
>
> 	The sense of the single letter options may be inverted by
> 	using `+' instead of `-'.  Some of the single letter option
> 	names refer to an option being off, in which case the
> 	inversion of that name refers to the option being on.  For
> 	example, `+n' is the short name of `exec', and `-n' is the
> 	short name of its inversion, `noexec'.
>
That's quite well written.  Throw in some examples and it's good. But 
one should not have to go hunting for that information.  Unless ... 
there is some heavy reason why that's needed, in which case there should 
be a note to that effect: "( The subject of options is so extensive that 
it requires it's own elaboration and can't be fully explained here.  
Please see 'zshoptions' in the manual for a full development of the 
topic.)" ... or something like that.
>
> The synopsis makes it quite clear that -A and +A can be used alone.
>
> 	set ... [ {+|-}A [ name ] ] ...

Clear to you but not to me.  I missed it.  The expert will always find 
the manual good enough but that's not the test.  The test is whether the 
student found it good enough.  (Mind, there will be times when the 
student, fallible human that he is, might miss something that really is 
well explained.  And to be honest, I think that's the case here -- it is 
good enough, but overwhelmed as I was by everything else, I missed the 
easy part.)  Again, I hardly expected to get it right the first time, 
that would be a miracle.  It was a template.

The only thing that matters is that I've got a few of you guys thinking 
about all this :-)





  reply	other threads:[~2022-12-22 14:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 22:41 manual Ray Andrews
2022-12-21  0:43 ` manual Lawrence Velázquez
2022-12-21  1:15   ` manual Ray Andrews
2022-12-21  1:44     ` manual Lawrence Velázquez
2022-12-21  4:15       ` manual Ray Andrews
2022-12-21  2:00 ` manual Daniel Shahaf
2022-12-21  4:12   ` manual Ray Andrews
2022-12-21  4:43   ` manual Bart Schaefer
2022-12-21 14:04     ` manual Ray Andrews
2022-12-22  6:31       ` manual Lawrence Velázquez
2022-12-22 14:20         ` Ray Andrews [this message]
2022-12-21  9:38   ` manual Lawrence Velázquez
2022-12-22  7:03 ` manual Lawrence Velázquez
2022-12-22 13:50   ` manual Ray Andrews

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=ccb7c9a1-d8ae-de33-f2d1-20b10e1187e1@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).