From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: Re: HIST_IGNORE_DUPS also ignores command lines that differ by a space between quotes
Date: Fri, 15 Mar 2024 13:53:17 +0100 [thread overview]
Message-ID: <20240315125317.GC3738413@cventin.lip.ens-lyon.fr> (raw)
In-Reply-To: <CAH+w=7aRd=J9onerixqEa+iSXL22++xPCA0kwWk5Y=mYgm9QPA@mail.gmail.com>
On 2024-03-13 22:13:09 -0700, Bart Schaefer wrote:
> On Wed, Mar 13, 2024 at 5:38 AM Vincent Lefevre <vincent@vinc17.net> wrote:
> >
> > With zsh 5.9, HIST_IGNORE_DUPS is buggy: it also ignores command lines
> > that differ by a space between (single or double) quotes.
>
> With zsh back to at least April 1, 2000 and probably sooner.
> Searching history with the ZLE widgets works the same way.
>
> Doing a full syntax analysis here would make it a lot more complicated
> and a lot slower.
I don't think you need to do a full syntax analysis. Isn't this just
related to tokenization (something like that)?
Note that spelling correction, which occurs *before* the line is put
in the history, detects quoted text and won't try to correct it. So
it seems that "quoted status" can be taken into account at that point.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2024-03-15 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 12:38 Vincent Lefevre
2024-03-14 5:13 ` Bart Schaefer
2024-03-15 12:53 ` Vincent Lefevre [this message]
2024-03-16 16:00 ` Bart Schaefer
2024-03-19 10:57 ` Vincent Lefevre
2024-03-19 11:08 ` Mikael Magnusson
2024-03-19 12:34 ` Vincent Lefevre
2024-03-20 17:46 ` Bart Schaefer
2024-03-20 17:48 ` Bart Schaefer
2024-03-20 23:48 ` Vincent Lefevre
2024-03-21 5:22 ` Jun T
2024-03-21 5:36 ` Bart Schaefer
2024-03-21 9:41 ` Jun T
2024-03-21 10:21 ` Vincent Lefevre
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=20240315125317.GC3738413@cventin.lip.ens-lyon.fr \
--to=vincent@vinc17.net \
--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).