From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21335 invoked from network); 22 Jun 1999 09:33:30 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 22 Jun 1999 09:33:30 -0000 Received: (qmail 10154 invoked by alias); 22 Jun 1999 09:33:14 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6777 Received: (qmail 10147 invoked from network); 22 Jun 1999 09:33:13 -0000 Message-Id: <9906220904.AA21791@ibmth.df.unipi.it> To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: collist v2.0 In-Reply-To: "Sven Wischnowsky"'s message of "Tue, 22 Jun 1999 10:25:34 DFT." <199906220825.KAA23802@beta.informatik.hu-berlin.de> Date: Tue, 22 Jun 1999 11:04:35 +0200 From: Peter Stephenson Sven Wischnowsky wrote: > - The behavior when asking if the list should be shown should be ok > now (I hope). Just as soon as I finished the last prompt I had a problem. With menucomplete set, - go somewhere with too many files - type `echo ' (without the quotes, of course) - answer n to the message - the first menucompletion match is inserted; hit TAB to go to the next - I don't know if this is significant, but the match was a directory with a slash; when I hit TAB, the next one wasn't a directory but appeared with a space after it - at that point everything freezes up and after some seconds the shell exits with the message `killed', maybe due to memory exhaustion? I almost reproduced the behaviour with zsh -f, menucomplete, and the standard set of new completions: in this case, the directory (it was Builtins) stayed in place, tab started menucompletion in the subdirectory, and again the shell froze and then exited after the first item. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy