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



On 5/1/2014 12:44 PM, Terry Hertel wrote:
For the most part I like the way the editor indents and formats CL. What I don't like is that it moves my comments (change notations) from the front of the command to the end, so added lines don't stand out as well, especially if the command spans multiple lines. And no, I do not display or the date column because it makes it hard to find all of the changes made for a specific request/project. I was thinking about submitting an RFE asking for an option that would allow comments entered in the space before the indent value to be frozen and not moved, but don't want to bother if others wouldn't be affected or support the request. What do others think?

First, I think there is an audience for the RFEs beyond this list. I
for one subscribe to the RFEs by email, so usually I see when one is
added. In addition, what you want might be a 5 minute change - who
knows? So you might want to put in the RFE anyway, just to document the
desire.

I myself don't use change notation comments, so I hadn't noticed how
they get reformatted. I also don't generally care for auto-formatting
beyond smart indentation, and so I turn that all off as well. If my CL
programs get complicated enough that I need special notation, I tend to
use that as an indicator (hah!) that it's time to use an HLL; at least
for the overly complex bits.

But every group has a different approach, and you might be surprised how
many people do it the same way as you do.
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.