zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Inconsistent usage of NOMATCH/NO_MATCH in documentation
Date: Tue, 25 Oct 2022 12:12:09 +0200	[thread overview]
Message-ID: <20221025101208.3yd6kmszrxdsfwur@sym.noone.org> (raw)

Hi,

while looking up something in zshall(1) I noticed that the option
NOMATCH is inconsistently written in two ways:

~ → man zshall | egrep -ni 'no_?match'
196:       INTERACTIVE_COMMENTS,   KSH_ARRAYS,   NO_MULTIOS,   NO_NOMATCH,   NO_NOTIFY,    POSIX_BUILTINS,
832:       •      File generation failures where not caused by NO_MATCH or similar options
3719:       and the option NOMATCH is set, an error results.
3823:       which case the word is deleted; or unless the NOMATCH option is unset, in which case  the  word
6059:              Overrides NOMATCH.
6166:       NOMATCH (+3) <C> <Z>
6173:              ment list instead of reporting an error.  Overrides NOMATCH.
7177:       -3     NO_NOMATCH

Please note that every occurrence but one uses NOMATCH (and its
negation) NO_NOMATCH, but (line 832) uses NO_MATCH.

Should we correct that for the ease of searching inside zshall? (Which
is actually how I noticed it because I searched for NO_MATCH first.)

Would do unless there's some opposition.

		Kind regards, Axel
-- 
PGP: 2FF9CD59612616B5      /~\  Plain Text Ribbon Campaign, http://arc.pasp.de/
Mail: abe@deuxchevaux.org  \ /  Say No to HTML in E-Mail and Usenet
Mail+Jabber: abe@noone.org  X
https://axel.beckert.ch/   / \  I love long mails: https://email.is-not-s.ms/


             reply	other threads:[~2022-10-25 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 10:12 Axel Beckert [this message]
2022-10-25 10:35 ` Peter Stephenson
2022-10-25 10:52   ` Axel Beckert

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=20221025101208.3yd6kmszrxdsfwur@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-workers@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).