Re: Show block nesting in CLLE source

[Dan <dan27649@xxxxxxxxx>]

Vern, if the preference you are talking about is found via Remote Systems /
Remote Systems LPEX Editor / IBM i Parsers / CL, then, yes, Automatic
indent was already checked.  I tried the LL block trick and that worked.
It's not my ideal solution, because I was hoping for a nested view using
the lines on the left of the source code, but this is good to know.

Another issue I think I've found.  In the same dialog, I have Automatic
formatting checked, and:
. Label position: 1
. Command position: 4
. Continued line indent: 16

The Label position works (I tried several settings), but the other two do
not.  Using the above settings, the first line of a command (with no label
and not within any do group) starts at column 15 and continuation lines
start at 30.  This is when I'm editing an existing source member that was
created/edited using SEU's formatting.

Curious, I created a new CLLE member in RDi, and all the statements I add
follow the preferences mentioned above.  Finding this, I went back to the
other CLLE member I was editing, went to the bottom of the source, and
entered lines after the ENDPGM statement.  The editor continued to format
per the "SEU style", so I guess these preferences don't matter unless
you're editing a brand new member.

- Dan

On Tue, Dec 5, 2017 at 9:55 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

> Hi Dan
>
> Have you tried the indenting of blocks for CL? It's in a preference. If
> you need to get the whole member to be indented with it, you can try
> putting LL on the first line and LL and the last line - the indent takes
> place in changed lines, and this changes the whole thing.
>
> There can be places where the indent isn't what is expected - I have to
> make some local adjustments, then get back to doing sections as needed.
>
> You could do this on a copy of the member, if you want to maintain the
> original layout. Just be sure to turn the indenting off if you need to.
>
> HTH
> Vern