From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23648 invoked from network); 6 Jun 1999 16:41:22 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Jun 1999 16:41:22 -0000 Received: (qmail 22849 invoked by alias); 6 Jun 1999 16:41:10 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2360 Received: (qmail 22838 invoked from network); 6 Jun 1999 16:41:08 -0000 From: "Bart Schaefer" Message-Id: <990606164055.ZM10330@candle.brasslantern.com> Date: Sun, 6 Jun 1999 16:40:55 +0000 In-Reply-To: <9906061413.AA22155@ibmth.df.unipi.it> Comments: In reply to Peter Stephenson "Re: Call for opinions on a couple of prospective zsh patches" (Jun 6, 4:13pm) References: <9906061413.AA22155@ibmth.df.unipi.it> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-users@sunsite.auc.dk Subject: Re: Call for opinions on a couple of prospective zsh patches MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 6, 4:13pm, Peter Stephenson wrote: } Subject: Re: Call for opinions on a couple of prospective zsh patches } } "Bart Schaefer" wrote: } > * Partial word motions in the face of mixed case, i.e. move the cursor to } > the next/previous capital letter InMixedCaseWordsLikeThisOne, including } > deletions that treat words this way. } } Well, in 3.1 you can do more sophisticated things by altering $CURSOR with } widgets already, so new builtins are not really necessary. Furthermore, } getting a complete set of functions with this alternative word behaviour } looks a slightly wasteful way of doing it (and if it's an incomplete set of } functions, I guarantee it won't have the one you want). Looking at it more closely, I see that Greg didn't supply backward motion, only forward motion and both forward and backward deletion. It wouldn't be difficult for me to add backward motion. However, as you point out: } ... forward-word puts the cursor *after* the non-word character ... and so does backward-word; both assume that there is at least one non-word character between words, which isNotTheCaseHere. So a simple change for something like WORDCHARS would leave the cursor in the wrong place on every motion. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com