Skip to content
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

Closed
jnardiello opened this issue Feb 28, 2015 · 5 comments
Closed

UltiSnips simply won't work #452

jnardiello opened this issue Feb 28, 2015 · 5 comments

Comments

@jnardiello
Copy link

Hi,
for some reason - which I haven't yet understood - UltiSnips isn't working at all for me.

my .vimrc:

" Snippets
Plugin 'SirVer/ultisnips'
Plugin 'honza/vim-snippets'
let g:UltiSnipsExpandTrigger="<c-k>"
let g:UltiSnipsJumpForwardTrigger="<c-b>"
let g:UltiSnipsJumpBackwardTrigger="<c-z>"

" PHP
Plugin 'StanAngeloff/php.vim'
Plugin 'tpope/vim-commentary'
" PHP Autocomplete
autocmd FileType php setlocal omnifunc=phpcomplete#CompletePHP
set completeopt=longest,menuone
let g:SuperTabDefaultCompletionType = "<c-x><c-o>"
Bundle 'shawncplus/phpcomplete.vim'
let g:phpcomplete_parse_docblock_comments = 1
let g:phpcomplete_complete_for_unknown_classes = 1

Vim version 7.4.52, python 2.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

@jnardiello
Copy link
Author

Actually, I just tried to:

  1. Move the php.snippet from bundle\vim-snippet\UltiSnips\php.snippet to UltiSnips\php.snippet - still nothing
  2. Rename UltiSnips\php.snippets to all.snippets AND it's now working. So, seems like a filetype issue. PHP Completion and linting is working thou so seems like something affecting only UltiSnips

@jnardiello
Copy link
Author

So, for the records... This fixed it:
https://bugs.launchpad.net/ultisnips/+bug/1067416

Looks like the plugin is broken without issuing those commands.

@SirVer
Copy link
Owner

SirVer commented Feb 28, 2015

How did you install the plugin?

@jnardiello
Copy link
Author

I use Vundle to handle all my plugins. I issued the :BundleInstall command.

I had the exact same issue on three different machines (all Ubuntu 14.04)

@SirVer
Copy link
Owner

SirVer commented Mar 2, 2015

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.

@SirVer SirVer closed this as completed Mar 2, 2015
rubdos pushed a commit to rubdos/ultisnips that referenced this issue Oct 21, 2017
Correct js vf ${1} snippet syntax error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants