zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: HIST_IGNORE_DUPS also ignores command lines that differ by a space between quotes
Date: Wed, 20 Mar 2024 22:36:51 -0700	[thread overview]
Message-ID: <CAH+w=7Y+i8cWYdOBfs2xMEqFFGf_4ucJFb-1ssRV3DZYUsXbVw@mail.gmail.com> (raw)
In-Reply-To: <BD4BCD20-11DD-449A-97D1-995606597DCA@kba.biglobe.ne.jp>

On Wed, Mar 20, 2024 at 10:23 PM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
> I think HIST_IGNORE_DUPS would work as expected even without
> HIST_REDUCCE_BLANKS if we use the information in chwords and
> hist_ring->words, as in the patch below, for example.

Doesn't that require HIST_LEX_WORDS to be set to poplulate ->words
when reading histfiles?  And further, would it not behave differently
for "print -s" vs. "print -S"?

This is more a concern when someone is using something similar to
per-directory history files or other fooling with "fc -p" or
zshaddhistory.  Maybe not much of a worry.


  reply	other threads:[~2024-03-21  5:37 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
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 [this message]
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='CAH+w=7Y+i8cWYdOBfs2xMEqFFGf_4ucJFb-1ssRV3DZYUsXbVw@mail.gmail.com' \
    --to=schaefer@brasslantern.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).