-
-
Notifications
You must be signed in to change notification settings - Fork 684
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
filetype detection not working #159
Comments
You are right, there is a step missing in the documentation - it only UltiSnips also needs that Vim sources files from the after/ directory. status fixcommitted Launchpad Details: #LPC SirVer - 2012-10-17 10:13:15 +0200 |
I just tried that but it didn't solve my problem. in my vimrc I have set runtimepath+=~/.vim/UltiSnips-2.2 I have created ths symlinks as you said, so I now have ~/.vim/after/plugin/UltiSnips_after.vim -> ~/.vim/UltiSnips-2.2/after/plugin/UltiSnips_after.vim As before, Ultisnips works when I edit a perl or bash file but I only get the "all" snippets although the filetype has been determined correctly. Launchpad Details: #LPC Frank Schwach - 2012-10-17 11:34:31 +0200 |
please try the following: cd ~/.vim/after/plugin/ and see if this really prints something. Maybe the link is dead. Second thing to try: Does that solve your problem? status incomplete Launchpad Details: #LPC SirVer - 2012-10-17 23:03:50 +0200 |
Thanks for your help SirVer, much appreciated! Thanks! Launchpad Details: #LPC Frank Schwach - 2012-10-18 11:22:44 +0200 |
Try to link the files from ftdetect/* also into ~/.vim/ftdetect (create If that works, let me know if you need both symlinks (after and Launchpad Details: #LPC SirVer - 2012-10-19 08:20:31 +0200 |
Done that but it hasn't changed anything. My ftdetect folder now has: UltiSnips.vim -> UltiSnips-2.2/ftdetect/UltiSnips.vim Launchpad Details: #LPC Frank Schwach - 2012-10-23 10:48:40 +0200 |
Seems like the FileType autocommand is not installed. I do not know why. Launchpad Details: #LPC SirVer - 2012-10-23 14:19:07 +0200 |
oh no, hang on my mistake - just realised that the paths in my ftdetect symlinks are not correct (missing ../). Corrected them and it now works!!! So, yes, that was the problem. Launchpad Details: #LPC Frank Schwach - 2012-10-23 14:37:57 +0200 |
Glad that we found the solution. Sorry for taking so long with this. I status fixcommitted Launchpad Details: #LPC SirVer - 2012-10-23 19:14:53 +0200 |
Could you please add the instructions on how to install ultisnips properly using vundle, pathogen and VAM? Launchpad Details: #LPC Flavius Aspra - 2012-12-14 16:15:05 +0100 |
I use neither of these plugin managers, so I cannot really provide this information. Basically Ultisnips is just a regular Vim plugin, so there should be no need to do anything special. I also gladly accept patches and additions to the documentation. Launchpad Details: #LPC SirVer - 2012-12-17 10:49:10 +0100 |
I also just ran into this issue. I used the current version from vim-scripts where this thing is not documented yet. Maybe it's time for a new release? Launchpad Details: #LPC Gregor Müllegger - 2013-02-02 02:33:08 +0100 |
Yes, you are right. It is about time to release a new version of Ultisnips. Launchpad Details: #LPC SirVer - 2013-02-02 09:08:25 +0100 |
I'm using Vundle and ran into the same issue. Adding the after/plugin and ftdetect symlinks did the trick. I.e. mkdir -p ~/.vim/after/plugin I have to say though, it would be very nice, if ultisnip would work out of the box with vundle without all that trouble. Cheers! Launchpad Details: #LPC Lemming - 2013-02-27 22:41:40 +0100 |
I am using vundle with ultisnips and have zero issues. I guess you have vundle wrongly installed . see VundleVim/Vundle.vim#16 Launchpad Details: #LPC SirVer - 2013-02-27 23:30:31 +0100 |
For those installing from vundle on 12.04 (with the vim 7.4 launchpad repo everyone seems to recommend), the following seems to fix the error: mkdir -p ~/.vim/after/plugin This differs from the above with the /UltiSnips/ which is what is currently what vundle installs and fixes the typo in ftdetext! Launchpad Details: #LPC Anton Melser - 2013-11-05 12:44:52 +0100 |
Anton, could you elaborate what you are talking about? Which typo? Vundle works perfectly fine with Ultisnips (if you install vundle correctly). Launchpad Details: #LPC SirVer - 2013-11-05 20:24:59 +0100 |
When installing it from github via vundle, the correct path is: ~/.vim/bundle/ultisnips/*. Above mentioned workaround is therefore: mkdir -p ~/.vim/after/plugin Only for the record :) Should be obvious, but I had trouble with it myself, so I wanted to make things clear! Launchpad Details: #LPC Zapata - 2013-12-30 16:53:49 +0100 |
This is also necessary for pathogen, but seems to be OS dependent -- same settings/plugins works fine on ms-windows without this fix. Launchpad Details: #LPC mMontu - 2014-02-04 17:19:08 +0100 |
The comment above has a typo (i.e. ftdetext), here is the corrected version:
|
Just installed UltiSnips from the tarball, on vimscripts version 2.2. It works but I only get the "all" snippets in files which are otherwise correctly identified by the filetype plugin as Perl and BASH files (filetype is correctly showing up in the status line and syntax highlighting and indentation work as before).
Manually adding the filetype with, e.g.
:UltiSnipsAddFiletypes perl
loads the perl snippets and all works correctly.
I have installed UltiSnips as suggested by extracting the tarball into a directory which I then added to the path in my .vimrc
I have seen the same error reported in conjunction with Vundle but I'm not using Vundle, so not sure what the problem could be or how to investigate this further. Thanks for your help!
my vim version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Apr 16 2010 12:40:58)
:py import sys; print sys.version
2.6.5 (r265:79063, Oct 1 2012, 22:19:00)
[GCC 4.4.3]
Launchpad Details: #LP1067416 Frank Schwach - 2012-10-16 18:15:45 +0200
The text was updated successfully, but these errors were encountered: