Re: LPEX editor "find" broken for some text

[adrian <stori@xxxxxxxxxx>]

Correct.

If there is no actual blank in the line, Ctrl+F won't find it.  This 
will indeed be the case for files for which trailink blanks were trimmed.

Christen, Duane J. wrote:
> One of the IBMrs could verify this but LPEX does not store trailing blanks
> by default, and thus does not find the string with the trailing blank. I
> think playing with the preference (window->preferences->lpex
> editor->save->trim trailing blanks) should be unchecked and the
> (window->preferences->lpex editor->save->maximum line length)should be set
> to something other than 0.
>
> [...]
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of 
> craigs-tksaTn4SAz0AvxtiuMwx3w@xxxxxxxxxxxxxxxx
> Sent: Thursday, May 18, 2006 7:17 AM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: [WDSCI-L] LPEX editor "find" broken for some text
> I have found a seemingly important case where the LPEX editor "find"
> (Ctrl+F) cannot find certain text if the input string contains any trailing
> spaces.  It just skips over them. [...]