Re: LPEX editor "find" broken for some text

Thank you!  I think I have a working solution.  That would also appeal the
free-form folks.  :)
One more thing worth noting though for maybe IBM.  Logically, it appears
that any source line containing an "=" sign in the factor 2 for ILE RPG
have blanks inserted to the end instead of being trimmed.  I say this
because the finding of text with a blank at the end finds text matching at
the end of lines with an "=".  You will have to search this list for my
original post because it was cut off later.  For example, Ctrl+F for "var2
" finds a line like "c      eval     var1 = var 2" even though trailing
blanks were supposed to be trimmed.  What is so special about the "=" sign?
Aren't those supposed to have their trailing blanks trimmed?  It's not like
we use the "=" sign very often in ILE RPG.  Ha ha :)

*** Adam wrote:
Give this a try:

Find:  begsr |begsr$

Make sure you check the 'Regular expression' box.  This translates as
"find the string 'begsr ' or the string 'begsr' at the end of a line".

Hope this is useful,
Adam



wdsci-l-bounces@xxxxxxxxxxxx wrote on 18/05/2006 03:45:33 PM:

>
> Thank you for your help everyone.  Okay, yes, I understand this.  But, I
> don't think that is much of a solution here.  I tested the settings
> mentioned and I have to add some spaces to the lines I plan on finding
in
> order to get it to work and then save.  So, I would have to add spaces
to
> the end of every line before saving in order to get it the way I want.
> Then there is the performance issue that trailing gives you in the first
> place.  Also, the inevitable case where someone else has save with trim
> trailing blanks set and undoes everything that was set.  I tried setting
it
> with trim trailing blanks set and it trimmed everything I did before.
What
> I am looking for is a setting to search in the LPEX editor window and
treat
> the blank space as spaces.  I want to find certain text and not text
that
> has characters afterwards.  This still seems like a problem without a
> practical solution to me.  I looked at other settings on searching or
> member opening and I don't see anything close.
> Do you think I should bring this problem up with IBM?  Any other ideas?
>
> ***Adrian wrote:
> 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. [...]