Sublime Forum

Dev Build 2162

#23

[quote=“jps”]Dev Build 2162 is out now. The next beta version should be out this week, so please let me know of any unresolved issues introduced in this series of dev builds.
[/quote]

“auto_match_enabled” works kind of funky: Suppose you have an empty buffer, type “))” and now place the cursor at the begging of the text (ie: “|))”, where | marks the cursor pos). Now try to insert a new parenthesis. You have to hit three times in order for the intended character to appear “)))|”, because each time you press “)” in that situation, it only moves the cursor one character to the left.

I’m not quite sure, but I think this used to work on early builds (< 2138 perhaps?).

I know the example is a bit weird, is just to make the problem obvious.
It usually bugs me when I need to add a closing parenthesis, square bracket, etc, just to the left of one of those characters. Example: “some_func((“missing parenthesis here->”|)”.

0 Likes

#24

This bugs me when inserting parentheses, too. For me it makes the most sense to use this keybinding: [code] { “keys”: “enter”], “command”: “move”, “args”: {“by”: “characters”, “forward”: true}, “context”:

    { "key": "following_text", "operator": "regex_contains", "operand": "^)\"\\]]", "match_all": true },
    { "key": "auto_complete_visible", "operator": "equal", "operand": false }
]   

}[/code]

instead of overriding the behavior of ", ), and ].

0 Likes

#25

I have found a bug…
The Side Bar will not refresh properly, when I close a tab and I have a folder/project and “View-> Side Bar-> Hide Open Files” enabled.

Tested on Windows and ST2 dev build 2150 - 2162

With “Show Open Files”, no problem.

With “Hide Open Files”, file highlight on sidebar show the bug.


Thank you

0 Likes

#26

Thank you for the update.

I noticed an issue that just came back, pressing shift + v to select the line then pressing k or the up arrow to select the rows above it as well now is deselecting the row you were on and just selecting the above ones again. Doing shift + v then j or the down arrow works as expected.

Many thanks!

0 Likes

#27

One more bug: Opening a Goto Panel (Ctrl+P, Ctrl+R, …) will save the file and not open the panel when save_on_focus_lost is enabled and the buffer is dirty.
The panel is opened when pressing the key combination a second time. I’ve been bitten by this on both Linux and the Mac.
The correct behaviour is probably to save the file and open the panel at the same time.
This issue has also been reported on UserEcho as a bug for build 2139.

Edit: sorry, just saw you were asking for bugs in this series of dev builds. You probably already know about all the other ones.

0 Likes

#28

Having serious performance issues with sublime text 2 (build 2162) and python. I’ve disabled all python related plugins. The cpu is pegged, and the response is extremely laggy. I haven’t seen this behavior in any of the previous builds.

If there is something I can do to help debug, let me know. Nothing of note shows up in the logs.

Edit: It was the show changes plugin.

0 Likes

#29

On Mac, the shortcut for fullscreen (on Lion) has been replaced by ‘Replace Next’ by default, annoying. Needs to move the mouse now to put ST in fullscreen.
Also, the Enter/Exit Free Distraction Mode also Enter/Exit fullscreen.

0 Likes

#30

Is commit_completion the only key I need to rebind back to Enter? I switch between far too many tools to have different keys for completion :smile:

0 Likes

#31

I think I found a bug with the autocompletion.

After hitting the tab key to autocomplete a function name, the autocomplete doesn’t automatically trigger for the function parameters.
I need to hit the ctrl+space to trigger the autocomplete for the function parameters. Previously, it was being triggered automatically.

I hope you can fix it, as the autocomplete is a real time saver.
Thanks!

0 Likes

#32

[quote]
After hitting the tab key to autocomplete a function name, the autocomplete doesn’t automatically trigger for the function parameters.
I need to hit the ctrl+space to trigger the autocomplete for the function parameters.[/quote]

I personally prefer enter for the accept completion key for exactly this reason plus the fact that enter is ingrained from other programs.

There was talk of using shift+enter/ctrl+shift+enter for snippet traversal in lieu of tab/shift+tab to alleviate this. That’s a lot of muscle memory to fight, for a lot of people though. Web forms all use tab/shift+tab for field movement.

What can you do?

0 Likes

#33

One of the many awesome thing about Sublime is how customisable it is!

Seems in the latest builds you can just use shift+enter to insert a \n in the case that the completion dialogue is open (having set as accept completion)

I personally don’t have the time to retrain to using tab so I’m stoked that it’s configurable.

0 Likes

#34

Why was using Enter for completions bad?

You could use completion inside snippets this way. While you moved through snippet points with TAB you could at the same time use completions with ENTER without interrupting the snippet.

This feature saved much time in my case (about 70% of the typing I do is inside a snippet). I think it should be at least configurable.

0 Likes

#35

I’m having issues with snippets.

After inserting a snippet like this:

@param {${1:String}} ${2:foobar} ${3:[description]}

The edit shows this:

@param {String} foobar [description]

And “String” is highlighted. Previously, pressing tab would just move to the next field (“foobar”), however now it is replacing “String” with a space first. Pressing it again will move to the next field, but a third time will clear that field, and so on. Here is the output from log_commands, starting with selecting the snippet:

command: commit_completion command: insert_best_completion {"default": " ", "exact": false} command: next_field command: insert_best_completion {"default": " ", "exact": false} command: next_field command: insert_best_completion {"default": " ", "exact": false}

Note that there were no autocomplete dialogs visible after the initial snippet insertion.

0 Likes

#36

Unable to reproduce this on Win 7 x64 with build 2161 or 2162. Bug reports should include your OS, the ST2 version when the functionality was last working and the ST2 version when it broke. Helps narrow down the cause much quicker :smile:

0 Likes

#37

For anyone who isn’t liking the new “tab” instead of “enter” for auto complete, you can stick this in your user keymap

{ “keys”: “enter”], “command”: “commit_completion”, “context”: { “key”: “auto_complete_visible” }] },

0 Likes

#38

[quote=“chrisguilbeau”]For anyone who isn’t liking the new “tab” instead of “enter” for auto complete, you can stick this in your user keymap

{ “keys”: “enter”], “command”: “commit_completion”, “context”: { “key”: “auto_complete_visible” }] },[/quote]

Thank you!

0 Likes

#39

I think Enter should still be the default for accepting completions.

I’m assuming the main issue comes into play with whitespace-based languages, or people who place open brackets on newlines. If I were one of those use cases, I would still prefer to hit Esc to cancel a completion instead of trying to re-train myself to use Tab to confirm a selection from a dropdown menu. Either that, or I would simply switch to Tab-based completion that cycles thru the available items.

Seems like this would be less of an issue if the auto-complete menu would hide once you’ve typed the only matching item in the list.

EDIT: After more time playing with the idea, the more I like tab. I like how it unifies snippets and completions into one list. Very, very cool… and I am sure more will come to this realization in time.

0 Likes

#40

// Controls if auto complete is shown when snippet fields are active. "auto_complete_with_fields": true,

yay!

0 Likes

#41

tito: Can you give some example text where the title case command isn’t working properly?

weslly: many thanks for the report, this is now fixed in 2163

ceej: I’m unable to replicate that, unfortunately

berndtj: sublimetext.com/docs/2/revert.html should fix any issues

spadgos: It’s working fine for me. Do you have any customised key bindings on tab?

0 Likes

#42

with default profile and this text:

asd asd as das a asd aswefewf we fwe fwe fwe f
Using title case on windows xp, latest sublime, text becomes:

Asd Asd as Das a Asd Aswefewf we Fwe Fwe Fwe F
Using suggested fix becomes:

Asd Asd As Das A Asd Aswefewf We Fwe Fwe Fwe F

0 Likes