From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2397 invoked by alias); 26 Jul 2016 16:00:56 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 38952 Received: (qmail 9157 invoked from network); 26 Jul 2016 16:00:56 -0000 X-Qmail-Scanner-Diagnostics: from mailout1.w1.samsung.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(210.118.77.11):SA:0(-1.3/5.0):. Processed in 0.128629 secs); 26 Jul 2016 16:00:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f4-f796c6d000001486-7d-57978933cb0f Date: Tue, 26 Jul 2016 17:00:48 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: bug with camel case and delete-whole-word-match function Message-id: <20160726170048.7de34262@pwslap01u.europe.root.pri> In-reply-to: <20160726165114.7ed32a3c@pwslap01u.europe.root.pri> References: <588168129.3340906.1467709726474.JavaMail.yahoo.ref@mail.yahoo.com> <588168129.3340906.1467709726474.JavaMail.yahoo@mail.yahoo.com> <20160726165114.7ed32a3c@pwslap01u.europe.root.pri> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsVy+t/xq7rGndPDDc62y1gcbH7I5MDoserg B6YAxigum5TUnMyy1CJ9uwSujMuHrjIXbGKpaDv2gLGBcQdzFyMHh4SAicSkzc5djJxAppjE hXvr2boYuTiEBJYySqxv28UCkhASmMEkcbTNDyJxjlHi/7VHUFVnGSX6Xz9nBKliEVCVmLX6 CBuIzSZgKDF102ywuIiAuMTZtefBJgkLuEp0fj3KCmLzCthLLDkzlR3E5hRwkJg+8yQTxNDj jBKLX8wAa+YX0Je4+vcTE8R99hIzr5xhhGgWlPgx+R7YUGYBLYnN25pYIWx5ic1r3jJDnK0u cePubvYJjMKzkLTMQtIyC0nLAkbmVYyiqaXJBcVJ6bmGesWJucWleel6yfm5mxgh4fxlB+Pi Y1aHGAU4GJV4eDlTpoULsSaWFVfmHmKU4GBWEuG91z49XIg3JbGyKrUoP76oNCe1+BCjNAeL kjjv3F3vQ4QE0hNLUrNTUwtSi2CyTBycUg2Mkd1WIgdtVQz27nl8KtVl3fEfnW9Mlu113h/u bnhku+ue7l0hXlkyLW/M/035cPXL68Znj2e5JTcsa8lZvd7axkr5yDLnFfdee4lKlG7/LG06 2VGr62U0R/vc/3Uia+5sLzs142FTiCf//C87nTzmrjN7Ebh5mQp7P/NNt8w9Cy6oveV5IH0z TImlOCPRUIu5qDgRAKweMdRjAgAA On Tue, 26 Jul 2016 16:51:14 +0100 Peter Stephenson wrote: > ...In addition > +the element tt(is-word-start) is 1 if the cursor is on the start > +of a word or subword, and 0 otherwise. Actually, if it's on a word start or after the end of the previous word, i.e. there could be intervening white space. This is OK if you want to operate on the next word by default, but could at least be documented better. Or it could be 0 = in middle of word, 1 = right at start of word, 2 = before start of word, or something. pws