Dev Build 2105

[que]

Setting highlight_active_indent_guide to false is not working for me.

[Anomareh]

Should project files named .sublime-project still be getting named .sublime-project.sublime-workspace?

Also with projects being the focus right now, are there any plans for projects remembering the state of the sidebar? Whenever I switch between projects I find myself having to minimize the Files/Groups sections and reexpand the folders I had open under Folders.

[oats]

An annoyance with recent versions: when I hit ctrl-F to "Find", the find panel is toggled up or down. I would rather ctrl-F always brings the find panel to the front. If I want to dismiss the find panel, ESC always works, and that's what I usually do. (It's a handy key that dismisses whatever panel, not just find.)

The problem I have is that I search for something, hit F3 a few times, and after reading some code, I sometimes forget if the find panel is the active panel or not -- when I hit ctrl-F to search for a new keyword, the find panel is hidden, and as I type the keyword I want to search for, it ends up in my text document instead.

[MrMartineau]

IMO it would be easier for me as a new user to decide I didn't like them and find the option to turn them off than it would be to discover they existed and the option to turn them on.

An annoyance with recent versions: when I hit ctrl-F to "Find", the find panel is toggled up or down. I would rather ctrl-F always brings the find panel to the front. If I want to dismiss the find panel, ESC always works, and that's what I usually do. (It's a handy key that dismisses whatever panel, not just find.)

Also with projects being the focus right now, are there any plans for projects remembering the state of the sidebar? Whenever I switch between projects I find myself having to minimize the Files/Groups sections and re-expand the folders I had open under Folders.

Totally agree with the above. +1 for each

[ajpalkovic]

Dev Build 2105 is out now, fixing a couple of project related regressions in 2104. Sorry about the project conversion issue in 2104 - I do try hard to avoid these kind of things.

If I were ever seriously worried about losing stuff, I wouldn't be using nightlys But I still appreciate the effort to not break stuff.

Small bug with the indentation guides, the active ones don't always show up on the whole column. Screenshot is below.

Additionally, as some people point out the active one shows up one tab higher than where they should. My screenshot shows that too.
I'm torn on this. On the one hand, I think it's smart to do that for normal statements. However, for lines that are indented, (like for loops, html tags) I hate it. Maybe you could use the grammar indent rules to determine if it should show the active guide one column higher or at the current column, if that makes sense. Like, if the indent rules say dont indent this line, then do what sublime does now. If the indent rules say indent the next line. then show the active guide at the beginning of the text, like the beginning of the for loop, not two spaces before the for loop.

Lastly, one last tiny bit of polish that would be nice if you're up for it. If a line is indented say 8 spaces and I click at column 2, it will draw an indent guide at column 6. I think if I click/arrow key before the first non-whitespace character, it should draw the indent guide where the cursor is. If I click after the first non-whitespace character, it draws the indent guide at that first non-whitespace character.

indentGuides.png (6.91 KiB) Viewed 475 times

[aparajita]

I haven't made up my mind if indent guides should be turned on by default or not - they seem popular, but can be visually distracting (IMHO, at least). I've attached a poll to this post - please let me know what you think.

If you took a vote I'll bet most people would want better highlighting of matching pairs than indent guides.

[digiduck]

If you took a vote I'll bet most people would want better highlighting of matching pairs than indent guides.

Gotta admit that I agree with this. The simple underlining takes quite a bit of focus to find right now. Definitely not something you can passively acknowledge.

[digiduck]

An annoyance with recent versions: when I hit ctrl-F to "Find", the find panel is toggled up or down. I would rather ctrl-F always brings the find panel to the front. If I want to dismiss the find panel, ESC always works, and that's what I usually do. (It's a handy key that dismisses whatever panel, not just find.)

+1

[Anomareh]

Additionally, as some people point out the active one shows up one tab higher than where they should. My screenshot shows that too.
I'm torn on this. On the one hand, I think it's smart to do that for normal statements. However, for lines that are indented, (like for loops, html tags) I hate it. Maybe you could use the grammar indent rules to determine if it should show the active guide one column higher or at the current column, if that makes sense. Like, if the indent rules say dont indent this line, then do what sublime does now. If the indent rules say indent the next line. then show the active guide at the beginning of the text, like the beginning of the for loop, not two spaces before the for loop.

Kinda hard to parse what you mean :s Maybe a picture? I think the expected behavior would be to check the character to the right of the guide, if it's whitespace or the end of the line show it, if it's anything else don't. Being able to see where lines that contain nothing but whitespace are indented to is really important, especially in languages like Python.

[ajpalkovic]

Additionally, as some people point out the active one shows up one tab higher than where they should. My screenshot shows that too.
I'm torn on this. On the one hand, I think it's smart to do that for normal statements. However, for lines that are indented, (like for loops, html tags) I hate it. Maybe you could use the grammar indent rules to determine if it should show the active guide one column higher or at the current column, if that makes sense. Like, if the indent rules say dont indent this line, then do what sublime does now. If the indent rules say indent the next line. then show the active guide at the beginning of the text, like the beginning of the for loop, not two spaces before the for loop.

Kinda hard to parse what you mean :s Maybe a picture? I think the expected behavior would be to check the character to the right of the guide, if it's whitespace or the end of the line show it, if it's anything else don't. Being able to see where lines that contain nothing but whitespace are indented to is really important, especially in languages like Python.

Let's say I have this code:

Code: Select all

TAB TAB if(true) {
TAB TAB TAB doSomething();
TAB TAB }


Right now, if I click anywhere on line 0 or line 2, sublime shows an active indent guide to the right of the first tab.
If I click anywhere on line 1, sublime shows an active indent guide to the right of the second tab.

I suggest this:
If I click before the if on line 0, it shows an active indent guide at the tab closest to where I clicked.
If I click anywhere at or after the if, it shows an active indent guide to the right of the second tab. (This is because the grammar would say that line 0 changes the indent of the next line, so it shows the active indent guide at that line. The idea is the active indent guide runs from the 'i' to the '}')

If I click before doSomething, it shows an active indent guide at the tab closest to where I clicked.
If I clicked on or after doSomething, it shows an active indent guide to the right of the second tab. (This is what sublime does now. The idea is this line does not change the indent level, show show the active indent guide at the 'parent scope').