× 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.



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.

Duane Christen

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of craigs@xxxxxxxxx
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.  I have done many tests in WDSC 6.0.1.1
on ILE RPG and CL members and I think I have limited it to the following
case:
The text occurs where there is no more text present on the line and where
there is no "=" sign present on the line.  It has to be "=", not "<", ">",
etc.  For ILE RPG, comments starting in column 81 don't matter.

For example, if you have any subroutines, search for "begsr ".   If you
have a select/endsl, search for "select ", "endsl " and you will see what I
mean.  Just type the text to search for and add a space.
This seems to be true for CL but I haven't done as many tests in CL as ILE
RPG.

This seems like a problem.  Anyone know of a fix?

Craig Strong


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.