plugin doesn't work

Bug #1275449 reported by tiny
This bug report is a duplicate of:  Bug #1067416: filetype detection not working. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UltiSnips
Incomplete
Undecided
Unassigned

Bug Description

When trying to expand or use any other mapping this plugin just doesn't work. Maps are clearly listed. Help is available but no joy.

Output of imap:
i <C-Tab> * <C-R>=UltiSnips_ListSnippets()<CR>
i <Tab> * <C-R>=UltiSnips_ExpandSnippet()<CR>
i <NL> * <C-R>=UltiSnips_JumpForwards()<CR>
i <C-K> * <C-R>=UltiSnips_JumpBackwards()<CR>

My input keystroke when editing a python file:
de<tab>
expands to:
de..

The output of :py import sys; print sys.version
2.7.5+ (default, Sep 19 2013, 13:52:09)
[GCC 4.8.1]

BundleList:
Bundle 'gmarik/vundle'
Bundle 'majutsushi/tagbar'
Bundle 'kchmck/vim-coffee-script.git'
Bundle 'pangloss/vim-javascript'
Bundle 'mattn/gist-vim.git'
Bundle 'wincent/Command-T'
Bundle 'tpope/vim-fugitive'
Bundle 'Lokaltog/powerline'
Bundle 'andviro/flake8-vim'
Bundle 'SirVer/ultisnips'
Bundle 'c.vim'
Bundle 'altercation/vim-colors-solarized'
Bundle 'tomasr/molokai.git'
Bundle 'squil/vim_colors.git'

Revision history for this message
tiny (ibabarovic) wrote :
Revision history for this message
SirVer (sirver) wrote :

de is no trigger.

try lorem<tab> and def<tab>. Also try <c-tab> (but make sure you are in gvim).

Changed in ultisnips:
status: New → Incomplete
Revision history for this message
tiny (ibabarovic) wrote :

Tried all that in gvim too. Nothing. How do I even debug this?

Revision history for this message
SirVer (sirver) wrote :

you can always printf debug by adding stuff into the vim or python scripts.

what happens when you press <ctrl-tab> (in gvim, this will not work on the console)? This should list all defined snippets.

what does :UltiSnipsEdit do?

If the mappings are set (and they are) everything should be working just fine. It could be that the filetype is not properly detected in case you have your vundle installed wrongly, but lorem<tab> should work in all cases (as it is defined in the all.snippets). I do not know all of the other plugins you have installed, so it could be that one of them is making trouble, but I doubt it.

Revision history for this message
tiny (ibabarovic) wrote :

I tried disabling all other bundles and it was still the same.

:UltiSnipsEdit

tries to edit all.snippets file but as I see it probably tries in the wrong place so that file is empty!
It's editing in
"~/.vim/UltiSnips/all.snippets"

instead of
"~/.vim/bundle/ultisnips/UltiSnips/all.snippets"

So this might be the key to this problem.

Revision history for this message
SirVer (sirver) wrote :

No, this is alright. what does <ctrl-tab> in gvim do?

Revision history for this message
tiny (ibabarovic) wrote :

Sorry, I thought I already explained it.
It does absolutely nothing. :(

Revision history for this message
SirVer (sirver) wrote :

okay, that is super strange. Obviously the plugin is found and sourced correctly since all the mappings are found. Maybe it is not finding any snippets.

try adding this to ~/.vim/UltiSnips/all.snippets

snippet test
this is a test
endsnippet

and try test<tab> in a new vim window.

otherwise you will need to reduce your configuration to a minimal .vimrc and only have UltiSnips in your path and then bring stuff back one by one to find out what breaks here.

Revision history for this message
tiny (ibabarovic) wrote :

Adding a test snippet into an empty ~/.vim/UltiSnips/all.snippets file works!
Test snippet works!

No other snippets in that directory though.

Revision history for this message
SirVer (sirver) wrote :

wait, what? that does work, but lorem<tab> does not work?

Revision history for this message
tiny (ibabarovic) wrote :

Sorry. Sincerely.
Lorem<tab> also works. I must have borked something.

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod
tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At
vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren,
no sea takimata sanctus est Lorem ipsum dolor sit amet.

But other stuff does not. So we're getting somewhere? :)

Revision history for this message
SirVer (sirver) wrote :

Sure. You messed up your installation of vundle most likely: https://github.com/gmarik/vundle/issues/16

Revision history for this message
tiny (ibabarovic) wrote :

You are absolutely correct sir!
Somehow while editing my vimrc I deleted "filetype off" line before vundle stuff.

Argh!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.