From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22593 invoked from network); 15 Dec 2003 19:21:17 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 15 Dec 2003 19:21:17 -0000 Received: (qmail 5879 invoked by alias); 15 Dec 2003 19:21:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 19291 Received: (qmail 5853 invoked from network); 15 Dec 2003 19:21:11 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 15 Dec 2003 19:21:11 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [4.11.8.53] by sunsite.dk (MessageWall 1.0.8) with SMTP; 15 Dec 2003 19:21:11 -0000 Received: (from schaefer@localhost) by candle.brasslantern.com (8.11.6/8.11.6) id hBFJL9u13505 for zsh-workers@sunsite.dk; Mon, 15 Dec 2003 11:21:09 -0800 X-Authentication-Warning: candle.brasslantern.com: schaefer set sender to schaefer@closedmail.com using -f From: Bart Schaefer Message-Id: <1031215192109.ZM13504@candle.brasslantern.com> Date: Mon, 15 Dec 2003 19:21:09 +0000 In-Reply-To: <1119.1071514226@csr.com> Comments: In reply to Peter Stephenson "Re: PATCH: widget called when zle starts." (Dec 15, 6:50pm) References: <1119.1071514226@csr.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: PATCH: widget called when zle starts. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Dec 15, 6:50pm, Peter Stephenson wrote: } } Are you demanding that sometimes when zle is started up, such as } for a continuation line, you want to maintain the current keymap? Yes. If you plow though the zsh-users thread, the request for zle to start in command mode was really a request for zle in vi mode to "act like vi" -- that is, start in command mode, but not leave insert mode until you explicitly press ESC. Pressing RETURN in vi to go on to the next line of input does not take you back to command mode, so I presume that the user wouldn't want the PS2 prompt in zsh to behave that way. And anyway, it'd be extremely confusing to have "select" loops start in command mode, because there's not normally even any history to scroll back through in that case.