From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28908 invoked from network); 25 Jun 2001 22:44:18 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Jun 2001 22:44:18 -0000 Received: (qmail 2607 invoked by alias); 25 Jun 2001 22:43:30 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15083 Received: (qmail 2586 invoked from network); 25 Jun 2001 22:43:28 -0000 From: "Bart Schaefer" Message-Id: <010625154301.ZM24246@candle.brasslantern.com> Date: Mon, 25 Jun 2001 15:43:01 -0700 In-Reply-To: <20010625213638.AE56C14286@pwstephenson.fsnet.co.uk> Comments: In reply to Peter Stephenson "Re: backward-kill-word behavior" (Jun 25, 10:36pm) References: <20010625213638.AE56C14286@pwstephenson.fsnet.co.uk> X-Mailer: Z-Mail Lite (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Subject: Re: backward-kill-word behavior MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 25, 10:36pm, Peter Stephenson wrote: > > We can supply functions that do this. The deletion is a trivial one-line > parameter substitution. However, pushing the deleted part onto the kill > ring appears to be rather harder. You can manipulate point and mark, but > that messes up the user's state. Is it really impossible to do this as the > internals do, or have I missed something? Is there something wrong with: function bash-backward-kill-word { local WORDCHARS='' zle .backward-kill-word } -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net