From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9802 invoked from network); 6 Mar 2000 07:00:09 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Mar 2000 07:00:09 -0000 Received: (qmail 21601 invoked by alias); 6 Mar 2000 06:59:41 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9996 Received: (qmail 21584 invoked from network); 6 Mar 2000 06:59:39 -0000 From: "Bart Schaefer" Message-Id: <1000306065935.ZM25884@candle.brasslantern.com> Date: Mon, 6 Mar 2000 06:59:35 +0000 X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: push-input, accept-and-hold, etc., and vared MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Using push-input or accept-and-hold during vared has unexpected (to me, at least) behavior -- to wit, the value of the variable is pushed onto the command input stack, and vared exits, whereupon the value of the variable is immediately popped into the PS1 editor buffer. There may be obscure circumstances in which this is what is meant, but (particularly in the case of "vared mapfile[...]") that's seldom so. I'm not precisely sure what to suggest we do about it, though. It might be nice to have accept-and-hold set the variable but not exit vared (this would be particularly useful with "vared mapfile[...]"). I'm at a loss with respect to push-input and friends. Perhaps they just shouldn't work? On a semi-related question, is it time that vared had its own keymap? The problem is initializing it properly, I suppose. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com