From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Inconsistent usage of NOMATCH/NO_MATCH in documentation
Date: Tue, 25 Oct 2022 11:35:17 +0100 (BST) [thread overview]
Message-ID: <1382638071.3650307.1666694117968@mail.virginmedia.com> (raw)
In-Reply-To: <20221025101208.3yd6kmszrxdsfwur@sym.noone.org>
> 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.)
Yes, that's quite definitely wrong. There's no MATCH option, it's NOMATCH,
so this is just plain confusing.
pws
next prev parent reply other threads:[~2022-10-25 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 10:12 Axel Beckert
2022-10-25 10:35 ` Peter Stephenson [this message]
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=1382638071.3650307.1666694117968@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--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).