Re: Weird formatting issue in LPEX when editing CL -- WDSCI-L

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

Subject: Re: Weird formatting issue in LPEX when editing CL
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Mon, 15 Feb 2021 09:56:06 -0600
List-archive: <https://archive.midrange.com/wdsci-l/>
List-post: <mailto:wdsci-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@lists.midrange.com?subject=unsubscribe>

On 9/22/20 10:51 AM, David Gibbs wrote:

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.

Turns out this particular bug manifests when auto-indent is turned on.

If I turn off auto-indent, it does not reformat the leading comment on ENDDO lines.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Weird formatting issue in LPEX when editing CL , Vern Hamberg

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.