From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3584 invoked from network); 26 Apr 2000 08:02:09 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Apr 2000 08:02:09 -0000 Received: (qmail 21923 invoked by alias); 26 Apr 2000 08:01:58 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10927 Received: (qmail 21897 invoked from network); 26 Apr 2000 08:01:56 -0000 From: "Bart Schaefer" Message-Id: <1000426080148.ZM16310@candle.brasslantern.com> Date: Wed, 26 Apr 2000 08:01:47 +0000 In-Reply-To: <200004260625.IAA09276@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: PATCH: Re: 3.1.7-pre-1: Problem with scrolled completion listings" (Apr 26, 8:25am) References: <200004260625.IAA09276@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: Re: 3.1.7-pre-1: Problem with scrolled completion listings MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 26, 8:25am, Sven Wischnowsky wrote: } Subject: Re: PATCH: Re: 3.1.7-pre-1: Problem with scrolled completion list } } > However, I'm confused. I don't want scrolling. I have LISTMAX=100, not } > LISTMAX=scroll. Yet still I get scrolling. } } That's why I first didn't give the list-prompt style a default } value. It specifies both the prompt to use and that scrolling is used } at all. But the doc still says to set LISTMAX=scroll (mod_complist.yo, lines 130-136) and doesn't say anything about _main_complete forcing it on (via compstate[list_max]=scroll) just because LISTPROMPT isn't empty, which appears to be what happens. This looks like a case of the doc reflecting the C code in the complist module, but the completion system establishing a different default. This is not good; there's no right way to document it. } We had the suggestion to allow going back in completion lists. I told you it was a bad idea to start implementing a pager. Drive a stake through it's heart right now or you'll pay in blood later. Leave it as is. I'm tempted to say we should even file it as a bug on SourceForge and then mark it closed with a "won't fix" status. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com