bulgrien wrote:While I agree with others in this thread that indent guidelines would be useful, I must point out that the screenshot above does not provide an indent guideline for the outer if block. I use smaller indents in my source code, so I wonder if indent guidelines would end up cluttering my display unnecessarily. Perhaps showing the indent guideline when a user clicks on an open or close brace would be a nice compromise... that way a user can make one appear when it would be helpful, but not have them there at every indent level all the time.
Well, the feature is already implemented in this next release, so it would be doubtful that they would make this change up front. You might consider sending in a feature request to make that a configurable option. "On all the time" or "On only for the indent area the cursor is currently residing in." Right now it's "on or off" only. Using an "open or close brace" click would be difficult to implement, since not all languages fold/indent using a brace (the language I give in my screenshot below, for example, which is Object Pascal.)
I, personally, want the indents there all the time. I have altered the color to be more subdued to where they don't stand out loudly, but are there when I need them.
I use an indent level of "2 spaces". The guidelines work beautifully with that indent level, at least for me.
Here is a clip of a screenshot I took. I don't give the whole application window, because this is all you need to see it, and I try to respect the bandwidth of dial-up users, as there are still many in this world. Pardon my "green Matrix" look, but it's easy on my eyes for long hours of work. I've learned that multiple colors distract, so I use "shades" of one color for syntax highlighting.
![]()
