From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH?] Re: Autocorrect for commands with a hyphen (dash) in the name
Date: Sat, 23 May 2020 20:44:27 +0100 [thread overview]
Message-ID: <22f19bb4707e388629092d2e8673d8294fa8e375.camel@ntlworld.com> (raw)
In-Reply-To: <CAH+w=7a=AB5ksiU7Tv2A3xnr2TVd=LAfQ--M0B=Vq56T_k+xyA@mail.gmail.com>
On Sat, 2020-05-23 at 12:33 -0700, Bart Schaefer wrote:
> [Moving to -workers from -users]
>
> On Tue, May 19, 2020 at 2:25 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> >
> > So, the following? Or should this also have the equivalent of
> >
> > if (*w == Tilde || *w == Equals || *w == String)
> > *x = *w;
> >
> > like zle_tricky.c?
>
> Any comment on this?
I don't think you need to put back tokens. If the spell check worked,
the result is just a normal word. If the spell check didn't work, just
leave it the way it originally was --- that may need some work but I'd
say it was a better bet than removing and re-adding tokens, which is
bound to hit some nasty cases.
pws
next prev parent reply other threads:[~2020-05-23 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOoO2vg=-9P7v=ATOzrbh6VF35o_xzK_-yF+EA6OgTHsQBik-A@mail.gmail.com>
[not found] ` <CAH+w=7bKpm7GO2ZhbA5Apr0sBDz5=kmX1=WK2X0nTcWxpkHPPQ@mail.gmail.com>
[not found] ` <ab8b7655-83e8-45b2-889f-043314faea62@www.fastmail.com>
[not found] ` <CAH+w=7aqAO37qpSvtmJXMPWq3zP=pUAZCe3i-BFyn0knRmFjVQ@mail.gmail.com>
2020-05-23 19:33 ` Bart Schaefer
2020-05-23 19:44 ` Peter Stephenson [this message]
2020-05-23 19:54 ` Bart Schaefer
2020-05-23 20:30 ` Peter Stephenson
2020-05-23 21:18 ` Bart Schaefer
2020-05-24 17:11 ` Peter Stephenson
2020-05-24 18:39 ` Bart Schaefer
2020-05-25 5:46 ` Bart Schaefer
2020-05-25 16:35 ` Peter Stephenson
2020-05-25 21:45 ` Bart Schaefer
2020-05-30 21:25 ` Bart Schaefer
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=22f19bb4707e388629092d2e8673d8294fa8e375.camel@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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).