From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16209 invoked from network); 12 Feb 2002 19:31:02 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 12 Feb 2002 19:31:02 -0000 Received: (qmail 17720 invoked by alias); 12 Feb 2002 19:30:57 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16616 Received: (qmail 17708 invoked from network); 12 Feb 2002 19:30:57 -0000 Date: Tue, 12 Feb 2002 11:30:27 -0800 (PST) From: Wayne Davison X-X-Sender: To: Derek Peschel Cc: Subject: Re: why is 2 the smallest HISTSIZE? In-Reply-To: <20020212045901.A10430@eskimo.eskimo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 12 Feb 2002, Derek Peschel wrote: > Setting HISTSIZE to zero would disable the history list -- are there > any other ways of disabling it? One (drastic) way to disable it is to "unsetopt zle". Of course, it disables all the fancy command-line editing as well. > but the code prevents HISTSIZE from actually becoming zero. I guess > that prevention is what creates the illusion of a "last comamnd" > buffer (Is there a separate buffer, not maintained by the history > mechanism?). Right (there's no separate buffer). > Did the implementation (of the "last command" buffer) change, but the > 2 not get changed to 1? Yeah, looks like I overlooked this "2" value. I'll fix this. ..wayne..