Re: LPEX editor "find" broken for some text -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Correct.

If there is no actual blank in the line, Ctrl+F won't find it. Thiswill 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. [...]

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.