[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: XPL questions
- Subject: Re: XPL questions
- From: "Robert Holmgren" holmgren@xxxxxxxx
- Date: Sun, 3 Sep 2006 00:09:30 -0400
** Reply to message from Harry Binswanger on Sat, 02 Sep 2006
22:52:02 -0400
> To explain this behavior, all I can think of is that {CR} is actually two
> bytes. But if you SEarch for just not-CarriageReturn, CarriageReturn, it
> works as expected.
The two bytes is key. SEarch for {not}{cr} by itself, and it jumps two bytes.
> I've found a number of times when I try to use a CI /// with both
> wildcards (especially the wild-W) and a carriage return or two that I get a
> spurious error message about wildcards having to be in the same order in
> the search and replace.
Example? (ENCODE it -- let's see the XPL, and also sample text that you want
to CI...)
-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------