From: Clint Adams <clint@zsh.org>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-workers@sunsite.dk
Subject: Re: correction hook
Date: Mon, 11 Feb 2002 11:38:28 -0500 [thread overview]
Message-ID: <20020211163828.GA17897@dman.com> (raw)
In-Reply-To: <20020211130457.70106.qmail@web9307.mail.yahoo.com>
> Aliases have served me well for the few common typos like this. I have
> reservations about this because this simple function probably doesn't
> go far enough. How might you disable correction for certain words, e.g.
> the destination to a mv command?
Sorry, I described a specific case and forgot to mention the more
general problems. They are as follows.
1) In the case of mak/mawk/make, the user has no instances of 'mawk'
in his history, but he has recently typed 'make'. The correction
algorithm is unaware of these details.
2) When one has CORRECT_ALL set, correction isn't nearly as intelligent
as completion. I have things like
alias cp='nocorrect cp'
alias mkdir='nocorrect mkdir'
alias mv='nocorrect mv'
Rather than adding a slew of additional aliases, it would be nice if
correction were smart enough not to assume that arguments to, f.ex.,
ssh should match local files.
> I'm not entirely convinced by the correction mechanism because it has
> to interrupt you with its prompt. With the new completion system I get
> any typo in a word I completed corrected by _approximate anyway. I'd be
> more inclined to think about a totally different way of spotting and
> communicating typos such as using the completion system continually and
> underlining possible typos.
I imagine that would be slow, though quite useful to some.
next prev parent reply other threads:[~2002-02-11 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 8:08 Clint Adams
2002-02-11 13:04 ` Oliver Kiddle
2002-02-11 16:38 ` Clint Adams [this message]
2002-02-11 19:14 ` Bart Schaefer
2002-02-11 13:48 ` Peter Stephenson
2002-02-11 13:55 ` Peter Stephenson
2002-04-07 16:51 Felix Rosencrantz
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=20020211163828.GA17897@dman.com \
--to=clint@zsh.org \
--cc=okiddle@yahoo.co.uk \
--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).