From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20002 invoked from network); 1 Jul 2009 11:44:11 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from new-brage.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.254.104) by ns1.primenet.com.au with SMTP; 1 Jul 2009 11:44:11 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 54254 invoked from network); 1 Jul 2009 11:44:03 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 1 Jul 2009 11:44:03 -0000 Received: (qmail 11925 invoked by alias); 1 Jul 2009 11:43:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 27081 Received: (qmail 11905 invoked from network); 1 Jul 2009 11:43:51 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 1 Jul 2009 11:43:51 -0000 Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by bifrost.dotsrc.org (Postfix) with ESMTP id DAE958027106 for ; Wed, 1 Jul 2009 13:43:47 +0200 (CEST) Received: by ewy18 with SMTP id 18so944977ewy.45 for ; Wed, 01 Jul 2009 04:43:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=X+W3r0TV+8XZX4Rf9dDPH9tVbgrzNLtH1L9O/rR8nPk=; b=pvGMohh1Oc4SroOU7LZsgpWAKjrfqlpd3hECpYV10z+nRZSLWMhBK0D0nc6TuX+un7 Myf33vynfNxnnDVBpa6tyBayzouVMzyH9M/6YnbMihaaJcwfnMxC1Nq8b/asYzSbORVJ 0DEti21YMcOmsbnLBtpVf7ABJwU+JPUwQfYk4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=KG3FapMJXx8VBZXr0t3sECIF0X4kgHTuWNXeeSc1ocaXTjKioPvYshx0yuKDz58GYv bfbdv4lO1O2ZI+/uMeEcRGsZR9M7T68aLaQ22TO1nYcby/Kt8dtaafKLs/y+XqZ84iev dMkxFfwJ/KGm3fT48L12Bk2GN5ucjUBiBxNt8= MIME-Version: 1.0 Received: by 10.210.140.16 with SMTP id n16mr76748ebd.27.1246448627095; Wed, 01 Jul 2009 04:43:47 -0700 (PDT) In-Reply-To: <200907011131.n61BVFuT000608@news01.csr.com> References: <200907011131.n61BVFuT000608@news01.csr.com> Date: Wed, 1 Jul 2009 13:43:47 +0200 Message-ID: <237967ef0907010443u4fcc28e4y65d768601c0419f5@mail.gmail.com> Subject: Re: PATCH: problem accepting completion in menu selection From: Mikael Magnusson To: Zsh hackers list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV 0.94.2/9531/Wed Jul 1 07:09:17 2009 on bifrost X-Virus-Status: Clean 2009/7/1 Peter Stephenson : > I've been having a problem for some time now that when I'm in menu > selection (menuselect keymap) and use return (or anything bound to > accept-line) to accept a completion: that doesn't happen, instead the > list is scrolled. =C2=A0Space is the other obvious thing to use to accept= the > completion and start typing a new argument, but it scrolls too, so this > is especially frustrating (it's only supposed to be special in > listscroll---as far as I can see listscroll is OK). > > You can accept the completion implicitly by typing another key, such as > a self-insert character other than space. =C2=A0I have absolutely no idea= how > space managed to be treated specially but I think it's because within > zrefresh() list-scrolling kicks in if the list is still active, which it > shouldn't be any longer, which is the fundamental problem. =C2=A0Even if = you > successfully accept the completion, however, it's not doing quite the > right thing, for example you don't get always_last_prompt behaviour. =C2= =A0I > think it's going through a series of baroque displays that top anything > Johann Bernhard Fischer von Erlach managed in his entire illustrious > career, ending up with nothing else to do other than the normal action > of the command which caused selection to exit and which was pushed back > onto the command stack, and which finally causes selection to be no > longer active but in a slightly awkward fashion. > > It's a little curious that no one else has noticed this; I assumed it > was due to some odd key binding I had but I see no evidence it is. I think I've noticed what you're talking about, I have menu selection for `kill` pid completion, but I usually just press ctrl-c to abort the list mode after i press enter to accept. I'll keep an eye out for regressions. --=20 Mikael Magnusson