From: "Matt Wozniski" <godlygeek@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Unexpected side effect of 'setopt correct'
Date: Sun, 5 Aug 2007 22:36:38 -0400 [thread overview]
Message-ID: <17393e3e0708051936m388bf6e4pdca167f03b8dcd5c@mail.gmail.com> (raw)
I just noticed this effect of 'setopt correct'.. Is this intentional behavior?
~> zsh -f
mastermind% setopt correct
mastermind% pid() {
zsh: correct 'pid' to 'pic' [nyae]? %
mastermind% function pid() {
function>
mastermind%
Is it intentional that it attempts to correct on a function
definition? Is it intentional that it only attempts to correct one of
the two types of function definition? Something about this behavior
caught me off guard. :)
~Matt
next reply other threads:[~2007-08-06 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 2:36 Matt Wozniski [this message]
2007-08-13 20:07 ` Peter Stephenson
2007-08-13 20:42 ` Matt Wozniski
2007-08-13 21:24 ` Peter Stephenson
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=17393e3e0708051936m388bf6e4pdca167f03b8dcd5c@mail.gmail.com \
--to=godlygeek@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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).