From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-workers@sunsite.dk
Cc: Vincent Lefevre <vincent@vinc17.org>
Subject: Re: [4.0.2 bug] commands not written to history
Date: Sun, 22 Jul 2001 13:11:09 +0200 [thread overview]
Message-ID: <20010722131109.A1129@ay.free.fr> (raw)
In-Reply-To: <1010722034119.ZM11228@candle.brasslantern.com>
On Sun, Jul 22, 2001 at 03:41:19 +0000, Bart Schaefer wrote:
> } because I ignore immediate dups:
> }
> } Shell 1: true a
> } Shell 2: true b
> } Shell 1: true a
> } Shell 1: true c
> }
> } Though after the last "true a", "true c" has been typed immediately
> } after it, the HISTFILE contains
> }
> } true a
> } true b
> } true c
> }
> } Is it possible to have immediate dups in the HISTFILE, but not in
> } the shell history?
>
> Not for duplicates occurring in the same shell. That is, you might get
> two `true a' in a row written out by different shells -- though they'd
> collapse to one when the $HISTFILE exceeded $SAVEHIST lines by a large
> enough margin to cause zsh to re-read/write it -- but in any given shell,
> the duplicate is thrown away before the check for unsaved commands is
> done.
What I wanted to say is: Could we have an option so that dups are
ignored in the shell history but not in $HISTFILE, so that we couldn't
have the above behaviour (useful when INC_APPEND_HISTORY is set)?
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
next prev parent reply other threads:[~2001-07-22 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010629163348.A9632@greux.loria.fr>
[not found] ` <20010721154449.A1971@ay.free.fr>
2001-07-21 18:32 ` Bart Schaefer
2001-07-21 23:43 ` Vincent Lefevre
2001-07-22 3:41 ` Bart Schaefer
2001-07-22 11:11 ` Vincent Lefevre [this message]
2001-07-22 13:39 ` Vincent Lefevre
2001-07-22 13:49 ` Vincent Lefevre
2001-07-22 15:33 ` 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=20010722131109.A1129@ay.free.fr \
--to=vincent@vinc17.org \
--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).