From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2457 invoked from network); 27 Jun 2001 14:02:09 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Jun 2001 14:02:09 -0000 Received: (qmail 3270 invoked by alias); 27 Jun 2001 14:01:20 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15129 Received: (qmail 3250 invoked from network); 27 Jun 2001 14:01:19 -0000 Message-ID: To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: backward-kill-word behavior In-reply-to: "Clint Adams"'s message of "Wed, 27 Jun 2001 09:41:44 EDT." <20010627094144.A10023@dman.com> Date: Wed, 27 Jun 2001 15:01:35 +0100 From: Peter Stephenson Clint Adams wrote: > > Is there something wrong with: > > > > function bash-backward-kill-word { > > local WORDCHARS='' > > zle .backward-kill-word > > } > > Not for the purpose in question. Should this go into > the FAQ or distribution? I'd suggest adding a complete suite of forward and backward move and kill functions to the Functions/Zle directory and documenting them in the user-supplied part of the manual. They'll be much more widely used than anything more general I get around to doing with patterns. -- 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. **********************************************************************