From: Bart Schaefer <email@example.com> To: Perry Smith <firstname.lastname@example.org> Cc: Zsh Users <email@example.com> Subject: Re: Trying to learn ... RCS and GLOBAL_RCS Date: Sat, 26 Mar 2022 10:05:25 -0700 [thread overview] Message-ID: <CAH+w=7bGTyg_W4yFnRtFBjHMQ6GtGnsuqHz1SS4oediPJkM5uQ@mail.gmail.com> (raw) In-Reply-To: <A9173145-A448-417F-BF49-F883EA030610@easesoftware.com> On Sat, Mar 26, 2022 at 9:45 AM Perry Smith <firstname.lastname@example.org> wrote: > > > On Mar 26, 2022, at 11:39, Bart Schaefer <email@example.com> wrote: > > > > Double negative. "unsetopt" shows the options that are not set, so > > "not no globalrcs" == "globalrcs". > > Oh dear… That is definitely where my confusing is coming from. History lesson time ... The zsh option naming convention was originally taken from csh. The most obvious example is the csh "nomatch" default that causes "echo foo*bar" to print "No match" when the globbing comparison fails. To turn off the "nomatch" behavior, you reversed it as "set nonomatch". This is because csh didn't have options with "off" state, it only had the default behavior and options that when set, changed the default behavior. Consequently a bunch of zsh options got named "nosomething" and to turn them off you would use "setopt nonosomething". At some point in the mid-90s it was the list consensus that documenting the options under their "nosomething" names was confusing, so the docs all got rewritten to use the "affirmative" names. The output of "setopt" and "unsetopt", however, continues using the "no" prefix based on the historic practice.
next prev parent reply other threads:[~2022-03-26 17:11 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-26 13:53 Perry Smith 2022-03-26 16:39 ` Bart Schaefer 2022-03-26 16:44 ` Perry Smith 2022-03-26 16:48 ` Bart Schaefer 2022-03-26 17:04 ` Perry Smith 2022-03-26 17:39 ` Mikael Magnusson 2022-03-26 17:05 ` Bart Schaefer [this message] 2022-03-26 17:18 ` Perry Smith
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='CAH+w=7bGTyg_W4yFnRtFBjHMQ6GtGnsuqHz1SS4oediPJkM5uQ@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Trying to learn ... RCS and GLOBAL_RCS' \ /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
Code repositories for project(s) associated with this 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).