From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4280 invoked from network); 18 Mar 2002 08:42:24 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 18 Mar 2002 08:42:24 -0000 Received: (qmail 8706 invoked by alias); 18 Mar 2002 08:42:15 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16852 Received: (qmail 8695 invoked from network); 18 Mar 2002 08:42:15 -0000 From: Sven Wischnowsky MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15509.43076.3491.557711@wischnow.berkom.de> Date: Mon, 18 Mar 2002 09:41:40 +0100 To: zsh-workers@sunsite.dk Subject: Re: (backward-)kill-argument (1/2 thanks 1/2 problem re-statement) In-Reply-To: <1020315163900.ZM2296@candle.brasslantern.com> References: <15505.46831.979708.369781@wischnow.berkom.de> <1020315153147.ZM2228@candle.brasslantern.com> <1020315163900.ZM2296@candle.brasslantern.com> X-Mailer: VM 6.95 under 21.5 (patch 3) "asparagus" XEmacs Lucid Bart Schaefer wrote: > ... > > Something like what you describe could be created in the same way that > the completion system itself was created -- built up one function at a time > for all the possible contexts that you want to recognize and operate on -- > but it does not currently exist. If I'm not completely mistaken, we even once talked about this (at least I remember me thinking about something similar). But the problem is that this would be very complicated to describe (statically) with all the different ways commands handle their arguments, plus run-time and operating system dependencies. Bye Sven -- Sven Wischnowsky wischnow@berkom.de