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



Buck wrote:
I'm a Code/400 guy, so I click on the source window (hate the mouse - can't
I F6 or something to move between panes?), press the escape key (to get to
the command line) and type 'find emphasis match Elapsed[a-z]' and get a
message that 'FIND' is not a command.  Oh, no.  The commands are different.

Yes, find is now findText, match is regularExpression. More keys to type, I'm afraid... Strongly recommend the find dialog, or /text on the command line for simple searches.


As for help: "help findText" (as an example) from the LPEX command line.

Is there a cross-reference from Code to jLpex commands anywhere?  I use the
command line A LOT.  A simpler findText works, but ctrl-n (for next) does
not.  Waaaah!

Underlying Eclipse steals Ctrl+N (and other keys). In Eclipse R2.1 (upcoming), which has a new key-binding mechanism in place, LPEX steals the Ctrl+N (and its other keys) back...


If you use the find dialog, another Ctrl+F (when the dialog is up already) will do a find next. Or you can bind another available key to the findNext action.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.