-
-
Notifications
You must be signed in to change notification settings - Fork 686
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
UltiSnips simply won't work #452
Comments
Actually, I just tried to:
|
So, for the records... This fixed it: Looks like the plugin is broken without issuing those commands. |
How did you install the plugin? |
I use I had the exact same issue on three different machines (all Ubuntu 14.04) |
I used Vundle for years and never had any issues with filetype detection. I believe your problem is that your vimrc is not correct. Vundle (or rather vim) is very finicky about the order of statements. See for example VundleVim/Vundle.vim#16. I doubt that this is an UltiSnips issue. Closing until new evidence surfaces. |
Correct js vf ${1} snippet syntax error
Hi,
for some reason - which I haven't yet understood - UltiSnips isn't working at all for me.
my .vimrc:
Vim version
7.4.52
, python2.7
Whenever I trigger
<c-k>
simply nothing happens.The only similar issue I found is this:
#264
But in my case it seems that the filetype is working correctly. Any idea? I'm really running out of options. I've used UltiSnips in the past without issues.
Thanks
The text was updated successfully, but these errors were encountered: