From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3800 invoked from network); 12 Dec 2004 21:44:58 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 12 Dec 2004 21:44:58 -0000 Received: (qmail 52323 invoked from network); 12 Dec 2004 21:44:52 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 12 Dec 2004 21:44:52 -0000 Received: (qmail 11247 invoked by alias); 12 Dec 2004 21:44:16 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 20623 Received: (qmail 11208 invoked from network); 12 Dec 2004 21:44:14 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 12 Dec 2004 21:44:14 -0000 Received: (qmail 51329 invoked from network); 12 Dec 2004 21:44:14 -0000 Received: from moonbase.zanshin.com (64.84.47.139) by a.mx.sunsite.dk with SMTP; 12 Dec 2004 21:44:12 -0000 Received: from toltec.zanshin.com (toltec.zanshin.com [64.84.47.166]) by moonbase.zanshin.com (8.13.1/8.13.1) with ESMTP id iBCLiA3V025503 for ; Sun, 12 Dec 2004 13:44:10 -0800 Date: Sun, 12 Dec 2004 13:44:10 -0800 (PST) From: Bart Schaefer Reply-To: zsh-workers@sunsite.dk To: zsh-workers@sunsite.dk Subject: Re: Strange _values completion on accept-and-menu-complete and menu selection In-Reply-To: <200412130006.56691.arvidjaar@mail.ru> Message-ID: References: <200412111311.27916.arvidjaar@mail.ru> <200412121915.34004.arvidjaar@mail.ru> <200412130006.56691.arvidjaar@mail.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Content-Disposition: INLINE X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63 X-Spam-Hits: 0.0 On Mon, 13 Dec 2004, Andrey Borzenkov wrote: > > Normally compstate[compound_word] would be unset, but "compvalues -i" > > would set it based on the parse. > > I still believe this is more general and should not be limited to _values Sure; compstate[compound_word] doesn't have to be read-only, any function that needs it could set it. It just seems correct and convenient to have compvalues set it automatically. > Here is updated patch (which also fixes initialization problem). There's one line of shell code where you have compstate[compound] but want compstate[compound_word]. No need to repost, but fix before commit. > This still has problems in completing nested calls to _values (should it > work?) I don't have time to debug carefully just now, but I suspect without any real evidence that compstate[compound_word] is becoming unset on return from the nested call and therefore is wrong for the subsequent selections for the outer call.