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



Kurt,

I don't know if this related or not...

But, a "SEU-CODER" complained to me about LPEX re-formatting the code for CL... He said it change the whole command, instead of the small part he was editing....
Our company policy requires us to mark all code changed... :(

I told him that was an option that he could "TURN-OFF" if he desired:
Windows>Preference>Remote Systems>Remote Systems LPEX>IBM i Parsers>CL

I had him turn off "Automatic formatting", and that solved it for him...

The part that perplexed me, is that you said 7-different commands in CL source....

So, I could be guess at the wrong thing. Just thought I would point this out, just in-case it *MIGHT* be related to your issue...

Just asking....

-Ken Killian-


-----Original Message-----
Subject: [WDSCI-L] Undo in CL

This has always bothered me, but today was the tipping point.

I made changes to 7 different commands in a CL source. I then stepped away from it and gave a presentation for about an hour. I come back to the CL, make a line change, realize I changed the wrong line, pressed ctrl-z to undo, and it undid -all- changes I made to the source today (the 7 previous commands as well as the current one).

Is there a way to get undo in CL to work like it does everywhere else? Does this bother other people?

I suppose this would be an RFE thing.

-Kurt

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.