email edit

[Kenneth Brody]

Quoting Jay R. Ashworth (Sat, 10 Nov 2007 13:40:38 -0500):

> On Sat, Nov 10, 2007 at 12:54:44PM -0500, Kenneth Brody wrote:
>> Quoting Jay R. Ashworth (Fri, 9 Nov 2007 23:06:30 -0500):
[...]
>> >lhsc   <A | N | "_" | "-" | "+" | "%"
>> >lhs    <{lhsc}
>> >rhsc   <lhsc
>> >rhs    <{rhsc} "." {*}
>> >email  <lhs "@" rhs
>> >
>> >But rhs, which should not match "baylink.", unless I misunderstand the
>> >edit language rather badly after 20 years... does.
>> >
>> >{matches} are greedy, I think, and that's fine, but rhsc doesn't
>> >*match* a dot.  What am I missing, folks?
>>
>> You are correct that rhsc doesn't match the dot, which is fine, because
>> rhs says that your string from rhsc must be followed by a dot.
>>
>> That is:
>>
>>     {rhsc} "." {*}
>>
>>       {rhsc}  accepts "baylink"
>>       "."     accepts "."
>>       {*}     accepts the trailing spaces
>>
>>     End-of-edit and end-of-field reached.  Edit passes.
>
> * matches nothing?  That's not what my 5.0 help says; it says "matches
> any single character".

Last I checked, space is a character.

> Oh yeah: I always forget: filePro treats all fields as space padded on
> the right to the full length of the field.  I need { not-a-space } at
> the end there.

By placing "{*}" (accept all characters) at the end of the edit, you
explicitly told filePro to accept all of the trailing spaces.

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com