From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2672 invoked from network); 18 Mar 2005 21:47:21 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 18 Mar 2005 21:47:21 -0000 Received: (qmail 56562 invoked from network); 18 Mar 2005 21:47:14 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 18 Mar 2005 21:47:14 -0000 Received: (qmail 21823 invoked by alias); 18 Mar 2005 21:47:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 21017 Received: (qmail 21810 invoked from network); 18 Mar 2005 21:47:12 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 18 Mar 2005 21:47:12 -0000 Received: (qmail 56257 invoked from network); 18 Mar 2005 21:47:12 -0000 Received: from dsl3-63-249-88-2.cruzio.com (HELO dot.blorf.net) (63.249.88.2) by a.mx.sunsite.dk with SMTP; 18 Mar 2005 21:47:08 -0000 Received: by dot.blorf.net (Postfix, from userid 1000) id 0FE50AB5D; Fri, 18 Mar 2005 13:47:07 -0800 (PST) Date: Fri, 18 Mar 2005 13:47:07 -0800 From: Wayne Davison To: Bart Schaefer Cc: zsh-workers@sunsite.dk Subject: Re: revisiting history-file rewriting Message-ID: <20050318214707.GB7372@blorf.net> References: <20050316204059.GA1298@blorf.net> <1050317180338.ZM32687@candle.brasslantern.com> <20050318181921.GF5500@blorf.net> <1050318211537.ZM1914@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1050318211537.ZM1914@candle.brasslantern.com> User-Agent: Mutt/1.5.6+20040907i X-Spam-Checker-Version: SpamAssassin 3.0.2 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=6.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2 X-Spam-Hits: -2.6 On Fri, Mar 18, 2005 at 09:15:37PM +0000, Bart Schaefer wrote: > Appending to the history writes in place, too, though, doesn't it? Or > at least incremental appending does? This option pertains to when the file is rewritten, which some modes only do accasionally (the incremental appending modes) and others do for their entire update strategy. > Maybe HIST_SAVE_BY_COPY, defaulting to on? Hmm. That's pretty good. The docs could clarify that the "SAVE" part just refers to when the file is rewritten, and does not affect incremental appending. ..wayne..