There is already truewordOffset available but you have to check
whether the search string is the next trueword.
So matchChunk is faster.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and
Hi.
Not sure, because I have never used one, but would a "trueWordOffset" help?
Craig
--
Sent from:
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
On 8/8/2019 5:18 PM, Dr. Hawkins via use-livecode wrote:
On Aug 5, 2019, at 7:43 AM, Paul Dupuis via use-livecode
wrote:
I'd like to see wholeMatches apply to:
Gee, that would do just what I need in searches . . . and the check is already
there, and applies in the IDE search/replace
On Aug 5, 2019, at 7:43 AM, Paul Dupuis via use-livecode
wrote:
>
> I'd like to see wholeMatches apply to:
Gee, that would do just what I need in searches . . . and the check is already
there, and applies in the IDE search/replace feature . . .
hmmm . . .
set the whole matches to true
Is it just me or would anyone else like to see the scope of the
wholeMatches property expanded beyond just wordOffset, itemOffset, and
lineOffset.
I'd like to see wholeMatches apply to:
Replace
Replace in field
Contains (as in if X contains Y)
With wholeMatches meaning test at white space
