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


  1.  Home
  2. WDSCI-L
  3. September 2020

Re: Weird formatting issue in LPEX when editing CL

Hey David - you probably also had to say to auto-format - turn that off for the time you enter this statement, then turn it on again - wish we had a switch for that, I don't know if a user-key could be set up for that.

Vern

On 9/22/2020 10:51 AM, David Gibbs via WDSCI-L wrote:
OK, this is kind of a weird one...

I'm editing a normal, OPM, CL ... everything is fine.  Nothing funky about the source member.

I want to put a comment in FRONT of a CL command.  For most of the source lines, everything is fine.

When I put the comment (/* xxx */) in front of an ENDDO command, LPEX automatically moves the comment after the command.

So I type in this:

/* xxxxx */     ENDDO

What LPEX formats it to is this:

                ENDDO /* xxxxx */

The only option for CL parsing I have enabled is automatic indent.

Any suggestions?  Is there a config option I'm overlooking.

david



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.