From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1659 invoked from network); 22 Jul 2001 13:22:17 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 22 Jul 2001 13:22:17 -0000 Received: (qmail 13712 invoked by alias); 22 Jul 2001 13:22:11 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15446 Received: (qmail 13701 invoked from network); 22 Jul 2001 13:22:10 -0000 X-Authentication-Warning: localhost.free.fr: lefevre set sender to vincent@vinc17.org using -f Date: Sun, 22 Jul 2001 13:11:09 +0200 From: Vincent Lefevre To: zsh-workers@sunsite.dk Cc: Vincent Lefevre Subject: Re: [4.0.2 bug] commands not written to history Message-ID: <20010722131109.A1129@ay.free.fr> Mail-Followup-To: Vincent Lefevre , zsh-workers@sunsite.dk References: <20010629163348.A9632@greux.loria.fr> <20010721154449.A1971@ay.free.fr> <1010721183220.ZM8456@candle.brasslantern.com> <20010722014311.A3932@ay.free.fr> <1010722034119.ZM11228@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1010722034119.ZM11228@candle.brasslantern.com> User-Agent: Mutt/1.3.19i X-Mailer-Info: http://www.vinc17.org/mutt_eng.html 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 - Web: - 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