Not respecting min length

[yajo]

Package autocomplete-plus has a default minimum word length of 3 characters, which is the one I am using:

However, this package starts autocompleting from the 1st character, which causes disturbing behaviors.

For example, if you write <a in an XML file, and you have a snippet called attrs (as is my case), you get this:

And then press TAB and you get the filled snippet:

But what I expected TAB to do is to expand the builtin <a snippet. I have to write <a, press ESC and then TAB to get that:

So maybe here we have 2 bugs:

1. No <a snippet completion displayed.
2. Not respecting configured minimum length.

[AlexandreDecan]

👍

I think I ran into a similar issue, see #78 for a complete description.

[AlexandreDecan]

I don't know Javascript nor Coffescript, but I think that something should be added at https://github.com/atom/autocomplete-snippets/blob/master/lib/snippets-provider.coffee#L21 (a comparison with the value defined in the settings). Right?

[divergentdave]

I think I ran into a similar issue. While inside a Python file, I typed a += p[Enter], and the p got replaced with import pdb; pdb.set_trace(). Disabling autocomplete-snippets fixed the issue.

This is particularly annoying for users of vim-mode-plus, since hitting escape to get rid of the autocomplete box also drops you out of edit mode.

[ArcusVonSinus]

Hi, is there some workaround? As in #78 I sometimes want to use tab to move to the next placeholder in a snippet, and if even a one-letter "word" gets autocompleted it is very annoying.

[msrd0]

Any update on this? I'm trying to reference a variable called n in an Octave script, what I get when I press tab or enter is

error(nargchk(min, max, nargin, `if [[ $TM_USE_OCTAVE -eq '0' ]]; then
	echo -n "'struct'"
fi` ));

That is REALLY ANNOYING. I don't want n to expand to that weird nargchk thing.