I've installed 2151 and found a bit annoying the autocomplete (using Ruby) so turned off. Now with 2152 and autocomplete off, doing "do(tab)" to get the usual "do |variable| ... end" snippet, it no longer works.

Now I need to enable autocomplete for it, but the dropdown of autocomplete gets a bit noisy when you actually know what you're doing and don't want autocompletion.

Also seems that the snippet changes from "do" as trigger to "dob", which could be what I'm seeing.

I only just noticed this, I don't know which update it actually changed in, but is there a reason why the recent file list no longer includes folders? If it was intentional and not a bug, can we have it back please?

Hmmm... The lastest update broke my plugin. Ironically, I believe it's from something that I requested:

Auto complete: Popup will be hidden if the word is erased

My plugin triggers autocomplete on period. In the lastest update, the autocomplete box disappears instantly. My only guess as to why is because ST2 looks at the previous character, sees it's a period and closes the autocomplete.

Also, there's a bug when typing on the last line with scroll_past_end turned off. Autocomplete pops up in the middle of the screen.

Other than that, the lastest version is fantastic. Thanks for all your hard work.

EDIT: In the meantime, I fixed this issue by adding an underscore to all my autocompletions and changing my plugin to insert

API: on_query_completions results may have tabs embedded in their descriptions, to deliminate help text

It would be nice if the help text wasn't considered while looking for a match to what is already typed.

I had modified SublimeRope so it's proposals have the form "proposal\t(help text)", but when on an empty line I start to type "func", the list of proposals that gets shown is, for example, "filter\t(builtin, function)", "format\t(builtin, function)"].

But if after I hit escape to close the popup, I hit ctrl+space, I get, for example "found_resource"] (that proposal doesn't comes from SublimeRope, but from the contents of the buffer).

In both cases I would expect to NOT have any proposals. In the first case, because I'm only interested in what is about to be inserted (not the help text). In the second, because if I had typed "func", "found_resource" is totally unrelated (the fuzzy search is just too fuzzy to be of any help).

Having "func" replaced by "found_resource" after I hit "." drives me insane (that's the reason I have "tab_completion" set to false, actually).

Edit: other than that, I really love ST2, and I'm trying to get my boss to buy us some licenses (hope that works out!).

I think we should be able to set which keys will accept the current autocomplete suggestion. As it is, every time I type "end" (which is practically every 3rd line in ruby) my "end" gets replaced with "send" and I have to go back and fix it. I love seeing the autocomplete box automatically, but I don't want it to replace my text unless I hit TAB.

As it is, every time I type "end" (which is practically every 3rd line in ruby) my "end" gets replaced with "send" and I have to go back and fix it. I love seeing the autocomplete box automatically, but I don't want it to replace my text unless I hit TAB.

+1 Better not hijack ENTER.

Regarding this comment, there is an issue with shift+tab, whatever the value of shift_tab_unindent settings:1. Start typing to show the autocomplete box.2, Validate your selection with tab key.3. shift+tab to insert tab -> doesn't work, do previous best completionI didn't find any way to insert a tab in this context. If I validate my selection with enter key it's working fine.Maybe the validation of autocomplete box with tab must react as validation with enter.

I've been using Beta for some time now. I downloaded the latest available Dev Build ( 2152 ) and noticed that my indent / unindent keybindings broke. I'm using a Mac and Spanish ISO Keyboard. { "keys": "super+]"], "command": "indent" }, { "keys": "super+"], "command": "unindent" }, These config works on Beta. On my keyboard I need to press the following keys: super+alt++ ( super+] ) super+alt+` ( super+ ) and they work. On DEV the default keys stopped working. If I change the ...