-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why 'g:SuperTabNoCompleteAfter' does not work ? #169
Comments
Can you provide more information? What do you have |
My setting is { let g:SuperTabNoCompleteAfter = ['^', ',', '\s'] } . When I start a new line(which means after nothing), I lost my literal tab. |
My g:SuperTabNoCompleteAfter is set to the default value, but it still opens a menu when I hit tab at the beginning of a line. |
i have the same problem, it works well when vim open. but after edit some files. the popup menu will be shown at the beginning of line( not all files) when tab hitted. |
maybe the reason is b:SuperTabNoCompleteAfter was overrided in some condition. i now use BufWinEnter autocmd to reset it when switching buffers. i'll keep to see if it's ok. ok,emmet-vim is the reason. after disable emmet, supertab works well in last few days. |
Supertab is awesome, but I lost my literal , which makes me uncomfortable, I tried 'g:SuperTabNoCompleteAfter', but it doesn't work.
Is it caused by my environment ?
my os is OSX 10.11.3, and vim version is 7.4.963, and I have the plugins of "
emmet-vim nerdtree supertab vim-fugitive vim-pathogen
indentLine snipmate.vim syntastic vim-nerdtree-tabs vim-powerline"
The text was updated successfully, but these errors were encountered: