×
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.
There appears to be no way to get syntax for CL the same in the jLPEX
editor as it is in SEU or even in CODE. With the settings at "lpex" and
"auto format", the editor will not, when I leave the line where the
statement is, keep changes I make. This is not unlike Visual Basic, except
that Visual Basic honors indents.
In SEU, if I format source as *I* want, it remains as I put it. Auto-format
takes over in jLPEX. In SEU, the only thing that will reformat is
pressing Enter after prompting (F4).
So I went to "seu" and turned off "auto-format". Changes I made were
retained, as long as I do not prompt. But taking the prompt, making
changes, and pressing OK makes it really weird - command starts in position
1, additional lines start in position 10.
And guess what? Taking Cancel, the formatting of the source is still
changed - Cancel means "leave it alone", doesn't it?
I do see that, with auto-format on and not using a prompt (how useless is
that? I rely on prompts), the formatting is similar to that of SEU, except
that the breakpoint for additional lines seems to be different - can live
with that, I guess.
But I will not use RSE for CL, at least for now.
Regards and holiday joys to all
Vern
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.
midrange.com
