g:SuperTabNoCompleteAfter is ignored

[busticated]

Hey there -

I noticed my SuperTab plugin started trying to complete when entering at the start of a new line.

Example:

define(['some/thing'], function(){
// pressing <tab> here invokes SuperTab when I really want a plain ol' <tab>
});

I use Vundle (and love it) to manage my vim settings. I did a BundleUpdate yesterday (5/4) and immediately noticed the new behavior. Prior to that, I think my last BundleUpdate was in March or thereabouts.

I have the following in my .vimrc:

g:SuperTabNoCompleteAfter=['^', ',', '\s']

When I check global variables from Vim via:

:let g:

I see the g:SuperTabNoCompleteAfter setting I expect.

Is there anything I else I can check / provide to help narrow down the issue?

[busticated]

More info:

Looks like this change introduced the issue: 47b82b6

Running this version works fine (up to but not including the above commit):

https://github.com/ervandew/supertab/tree/f5d028207f50c3d4d57c9ee2e83a5d7cd92933cd

[ervandew]

Take a look at #74 and let me know if you fall into the snipmate or similar camp, and if my one of my suggestions there works for you.

[busticated]

Ah, yes - that fixed it - thanks!

For others who may run into this, I found that the https://github.com/garbas/vim-snipmate branch introduced another problem (when tabbing in insert mode, I end up with <Plug>snipMateNextOrTrigger in my code >_<)

The https://github.com/ervandew/snipmate.vim branch works fine so far!

[ervandew]

Hmm, I couldn't reproduce any issues using the garbas/vim-snipmate code, though it was a bit annoying to see that they now require two other plugins as dependencies.

[busticated]

well, weird... it's probably some other thing unique to my setup then :-/ i'm thinking snipmate needs to get off the bus for a few stops here ;-)

thanks again for the help and an awesome plugin!

[muammar]

I had the same problem, and using https://github.com/ervandew/snipmate.vim as @busticated pointed out fixed it. Now my literal TAB is working normally.

[keithwissing]

I would recommend adding a note to the readme file about the incompatibility. It would have saved me a good bit of time, and I'm sure it would help others.