From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19648 invoked from network); 13 Mar 2000 09:22:55 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Mar 2000 09:22:55 -0000 Received: (qmail 4988 invoked by alias); 13 Mar 2000 09:22:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10102 Received: (qmail 4980 invoked from network); 13 Mar 2000 09:22:48 -0000 Date: Mon, 13 Mar 2000 10:22:46 +0100 (MET) Message-Id: <200003130922.KAA14988@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Oliver Kiddle's message of Fri, 10 Mar 2000 16:47:07 +0000 Subject: Re: Saving the zle display stuff Oliver Kiddle wrote: > Sven Wischnowsky wrote: > > > > It would be relatively easy to make it remember how long the list > > below the prompt is (it should already know about the presence of a > > list -- at least in most cases). > > So, are you suggesting a zle-option to make it put the prompt `below > > the list if there is one'? > > Yes: a zle-widget that puts the prompt below the list if there is one. > That allows me to keep the current list for later reference if I decide > that I want to. Hmhm. Dunno if/when I find the time... (or anyone else). > ... > > Out of interest, why does _setup use zstyle -s followed by [[ "$val" = > (yes|true|1|on) ]] for various things including last-prompt instead of > just using zstyle -b (or -t or -T)? Because it has to distinguish three cases: style not set, style set to `true', style set to `false'. > And in a separate message, Sven wrote: > > Oliver Kiddle wrote: > > > Is there a better way for me to have done the equivalent of :*:nothing:_nothing for the -r option? > > > > Can't think of a better way... never thought about that. Hm. Is it > > worth to make _arguments support this directly, i.e. add a syntax > > saying: `no more arguments after this option'? > > There's probably quite a lot of commands like zpty where they can be > used in a few separate ways (each with their own set of arguments) and > for these commands it is useful to avoid the final arguments for some > forms so if it is fairly simple to do and there is a clear way of > representing it in the _arguments parameters then it is probably worth > doing. Any suggestions for the syntax? (A trailing colon with no description after it?) Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de