From: Zefram <A.Main@dcs.warwick.ac.uk>
To: schaefer@nbn.com
Cc: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: Re: zsh.texi commentary (actually, HTML pages commentary)
Date: Fri, 21 Jun 1996 09:06:52 +0100 (BST) [thread overview]
Message-ID: <9856.199606210806@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <960621003054.ZM3580@candle.brasslantern.com> from "Bart Schaefer" at Jun 21, 96 00:30:52 am
>Aside: Filename generation: If you set both NULL_GLOB and NO_NOMATCH,
>which one wins?
NULL_GLOB. It actually beats any related option. Just as well too, as
this is relied upon in a number of places where NULL_GLOB is
temporarily set.
> What the heck happened to NO_NOMATCH when the change
>was made to make the prefix "no" into a magic equivalent of "unsetopt"?
>`setopt nonomatch' should be the same as `unsetopt nomatch', but what
>about `setopt nomatch'?? Why isn't it `unsetopt match'? Gaahhh. Or
>did I completely misunderstand what that was all about?
That patch isn't in the baseline yet. It made the canonical form of
that option NOMATCH, so that "setopt NOMATCH", "unsetopt NOMATCH",
"setopt NO_NOMATCH" and "unsetopt NO_NOMATCH" are valid. MATCH was not
made a legal option. I actually added quite a bit of text explaining
this to the zshoptions man page in the patch.
-zefram
next prev parent reply other threads:[~1996-06-21 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199606192106.XAA09696@bolyai.cs.elte.hu>
1996-06-19 23:42 ` zsh-2.6-beta21 released Clive Messer
1996-06-20 21:03 ` Mark Borges
1996-06-20 21:05 ` Zoltan Hidvegi
1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer
1996-06-21 8:06 ` Zefram [this message]
1996-06-21 12:15 ` Zoltan Hidvegi
1996-06-21 12:30 ` Clive Messer
1996-06-21 12:52 ` Zoltan Hidvegi
1996-06-21 15:55 ` Bart Schaefer
1996-06-21 16:59 ` Zefram
1996-06-21 17:22 ` Clive Messer
1996-06-21 17:32 ` Mark Borges
1996-06-21 17:45 ` Mark Borges
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=9856.199606210806@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).