Disable Ultisnips

Bug #1255075 reported by mMontu on 2013-11-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Won't Fix

Bug Description

Sometimes it is useful to disable Ultisnips, e.g., on machines where only Python < 2.6 is available. Currently one has to use the following to disable it:

   let g:did_UltiSnips_vim = 1
   let g:did_UltiSnips_vim_after = 1

Note that it is necessary to set two variables instead of one, and it differs from the "standard" g:loaded_ultisnips (`:h 41.11`).

I think it would be nice if the documentation included an explanation on this and/or it could be achieved through g:loaded_ultisnips.

SirVer (sirver) wrote :

Use Vundle and be done with that. This is out of the scope of this plugin.

Changed in ultisnips:
status: New → Won't Fix
mMontu (mmontu) wrote :

I don't know about Vundle, and it is not clear why the disabling of the plugin itself is out of its scope.
It is just that almost every plugin works that way, and it is recommended on Vim documentation itself.

Anyway, I'm fine with, I had already lost the time to find out the special name and the its unusual use on UltiSnips_after.vim.
It was just an attempt to improve the plugins so other users doesn't are forced to dig into the code or use Vundle.
Sorry if it upset you.

SirVer (sirver) wrote :

You didn't. It is just that you either install a plugin or you don't. If you want a plugin sometimes and sometimes not you should use a plugin manager. Setting this one variable will only disable parts of UltiSnips, i.e. the ftdetect hook is still installed. Vundle will disable it completely.

Vim's documentation is very old - a lot of the best practices in there are no longer true.

mMontu (mmontu) wrote :

I still don't agree with you on any of these points, but it is fine and I respect you.
Probably it is not worth our time to explain how my view differs from yours.

Thanks for pointing about ftdetect/UltiSnips.vim - that's so unusual that I've missed.
I'll include a check g:did_UltiSnips_vim on that file.

SirVer (sirver) wrote :

> Probably it is not worth our time to explain how my view differs from yours.

Well, if you do not lay out your arguments you will have a hard time convincing my of your point of view. Your call, of course :)

Generally speaking feature creep is to be avoided. My point is that there are specialized plugins that help with disabling other plugins when needed, so it makes more sense to defer to them instead of adding this functionality into each plugin that is out there.

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

Other bug subscribers