From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14525 invoked from network); 26 Jun 2001 14:00:52 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Jun 2001 14:00:52 -0000 Received: (qmail 218 invoked by alias); 26 Jun 2001 14:00:04 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15095 Received: (qmail 206 invoked from network); 26 Jun 2001 14:00:03 -0000 Message-ID: To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: backward-kill-word behavior In-reply-to: "Sven Wischnowsky"'s message of "Tue, 26 Jun 2001 15:24:39 +0200." <200106261324.PAA23185@beta.informatik.hu-berlin.de> Date: Tue, 26 Jun 2001 15:00:17 +0100 From: Peter Stephenson Sven Wischnowsky wrote: > Personally, I'd prefer it if we started moving more into shell code or > at least `prepare' that. So, how about adding a special array > `kill_ring' or whatever to the zleparameter module? Fine, but we will have to expose the ZLE_KILL flag so we know whether to overwrite or add to the existing buffer when user commands are mixed with internal kills. This problem is why (some time ago) Zefram was trying to decrease dependence on internal flags. The only other way is a different way of communicating this and other pieces of state information. Of course, we can do it completely separately, but then you're forced to replace all the internal kill commands with functions, which seems to me a bit much to force on people. We also need to decide how to rotate the kill ring if it's presented as an array. -- Peter Stephenson Software Engineer CSR Ltd., Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070 ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. **********************************************************************