Overrides default auto completion
When using this plugin it seems to override the default auto completion. For example, when typing <div class=" it will bring up the file name completion, rather than previous class names.
I'm not sure if I'm doing anything wrong, but my set up is pretty much the standard Sublime Text 2 install on Mac with a few plug-ins.
Cheers
I'm also getting this, also on a Mac. Seems the plugin will bring up a file autocomplete box on any string typed in any file, which gets a little annoying working with non-HTML files... The plugin is quite handy, but I don't really want it popping up every time I type a string.
Yes I'm having the same problem as markgoodyear, this plugin takes over the sublime native autocomplete feature as well as another useful plugin called "All Autocomplete" that extends native autocompletion from other opened files :(
I'm also experiencing this issue on Mac.
I would rather trigger its autocomplete by ctrl-x, ctrl-f, just like we did in Vim, but still use default autocompletion as usual.
I added a new setting if it gets in the way too frequently, you can set it to a keybinding so it doesn't get added into the default completion results. However, I consider this only a temporary fix. I plan on reducing the number of situations that it appears in and hopefully preventing it from removing the other completions.
These changes are only in the st3 branch.
Perfect, I was about to report this issue but now I see some already did it. Waiting for the fix, great work!
I would love to see this fix in a current stable release since it's taking awhile for ST3 to get released.
any updates to this? @evandrocoan any thoughts on fixing this in your fork?
It is a bug on Sublime Text core:
- https://github.com/SublimeTextIssues/Core/issues/819 on_query_completions fails to return custom completions when some characters are used
But I released some attempted fix to overcome this on my fork.