From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25662 invoked from network); 15 Mar 1999 09:36:12 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 15 Mar 1999 09:36:12 -0000 Received: (qmail 8 invoked by alias); 15 Mar 1999 09:35:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5794 Received: (qmail 29995 invoked from network); 15 Mar 1999 09:35:51 -0000 From: "Andrej Borsenkow" To: Subject: up-line-or-history and multiline input (was: RE: Debug / cut'n'paste on IRIX) Date: Mon, 15 Mar 1999 12:31:29 +0300 Message-ID: <001801be6ec6$9b135cf0$21c9ca95@mowp.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 I have a feeling, that these two are related ... Look at this (zsh-3.1.5-pws-12): bor@itsrm2:~%> for i in 1 2 3 4 for> do for> gives bor@itsrm2:~%> for i in 1 2 3 4 for> do for> setopt completeinword That is, when working with multiline input _every_ line is considered the "first and only" line of input by ZLE. I find it (and always found) very confusing. Even more, as you can go to previous line by using backward-char It is confusing, because when I recall the whole buffer, I *can* use up-line-or-history as expected. And it is related to multiline paste because if we treated the input as multiline, there would probably be no need to call trashzle at all ... cheers /andrej