Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: (backward-)kill-argument (1/2 thanks 1/2 problem re-statement)

X-seq: zsh-workers 16852
From: Sven Wischnowsky <wischnow@xxxxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: (backward-)kill-argument (1/2 thanks 1/2 problem re-statement)
Date: Mon, 18 Mar 2002 09:41:40 +0100
In-reply-to: <1020315163900.ZM2296@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <m2zo1cxvvl.fsf@xxxxxxxxxxxxxxxxxxxxx> <15505.46831.979708.369781@xxxxxxxxxxxxxxxxxx> <m2ofhsw728.fsf_-_@xxxxxxxxxxxxxxxxxxxxx> <1020315153147.ZM2228@xxxxxxxxxxxxxxxxxxxxxxx> <m2zo1996ga.fsf_-_@xxxxxxxxxxxxxxxxxxxxx> <1020315163900.ZM2296@xxxxxxxxxxxxxxxxxxxxxxx>

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@xxxxxxxxx

References:
- (backward-)kill-argument
  - From: Michal Maruška
- Re: (backward-)kill-argument
  - From: Sven Wischnowsky
- Re: (backward-)kill-argument -- reformulation of the problem
  - From: Michal Maruška
- Re: (backward-)kill-argument
  - From: Bart Schaefer
- Re: (backward-)kill-argument (1/2 thanks 1/2 problem re-statement)
  - From: Michal Maruška
- Re: (backward-)kill-argument (1/2 thanks 1/2 problem re-statement)
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author