From: Zefram <A.Main@dcs.warwick.ac.uk>
To: schaefer@nbn.com
Cc: A.Main@dcs.warwick.ac.uk, hzoli@cs.elte.hu,
clive@epos.demon.co.uk, mdb@cdc.noaa.gov,
zsh-workers@math.gatech.edu
Subject: Re: zsh.texi commentary (actually, HTML pages commentary)
Date: Fri, 21 Jun 1996 17:59:03 +0100 (BST) [thread overview]
Message-ID: <21470.199606211659@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <960621085558.ZM4927@candle.brasslantern.com> from "Bart Schaefer" at Jun 21, 96 08:55:54 am
>} 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.
>
>So you check for canonical forms before stripping off the leading "no",
>and then check again after stripping it to invert the sense? Or what?
Yes. I considered having it check for leading "no" first, but with
options NOTIFY and NOMATCH that wouldn't work.
>} Also these are builins now, which is not yet documented.
>
>Exactly what difference does that make? (Which is part of what ought to
>be documented ...)
That affects "disable exec"/"disable -r exec", and "x=ex; ${x}ec foo".
-zefram
next prev parent reply other threads:[~1996-06-21 17:07 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
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 [this message]
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=21470.199606211659@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=clive@epos.demon.co.uk \
--cc=hzoli@cs.elte.hu \
--cc=mdb@cdc.noaa.gov \
--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).