From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5692 invoked from network); 4 May 2000 15:34:53 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 4 May 2000 15:34:53 -0000 Received: (qmail 5084 invoked by alias); 4 May 2000 15:34:37 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11158 Received: (qmail 5067 invoked from network); 4 May 2000 15:34:37 -0000 Date: Thu, 4 May 2000 17:34:29 +0200 (MET DST) Message-Id: <200005041534.RAA12349@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Sven Wischnowsky's message of Thu, 4 May 2000 13:40:01 +0200 (MET DST) Subject: Re: PATCH: Re: History bug (Re: Completion debugging) I wrote: > Bart Schaefer wrote: > > ... > > > > > So there are still two 113s in the history list, but the prompt has the > > right history number. I'm expecting that particular shell to crash any > > time now ... > > I get a SEGV reproducibly after C-p C-n. If I take out my patch for > this, I get it after the C-p. > > Hm, maybe someone more knowledgeable with history stuff...? After playing some more and a couple of SEGVs later... There is so much mucking around curhist (and histline) in zle that I wonder if there is a clean way (other than changing the meaning of curhist in the core and then adapting zle). Maybe we should just make `print -s' put the strings added while zle is active into some list and then add those strings only after zle is left? I.e. in a toplevel-loop() or somewhere around that. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de