UltiSnips

Separate snippets from the engine

Bug #1162951 reported by Ian Liu Rodrigues
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UltiSnips
Confirmed
Wishlist
Unassigned
UltiSnips 2.3

Bug Description

UltiSnips is a great engine and I'm really pleased to use it.
But there is this annoyance that it comes with a lot of predefined snippets,
which not everyone might agree to fulfill their needs. For example, I often
use braces in-lined with "if" statements in my project.

I'm filling this bug report so UltiSnips split into two packages: one for the
engine itself, and another for snippets definitions.

Thanks,
Ian L. Rodrigues.

Revision history for this message
SirVer (sirver) wrote :

Thanks for the report. Some comments:

1) This is already planned and is a step needed for the merging of UltiSnips and snipMate that is still ongoing.
2) You can currently use 'clearsnippets' as first line in your snippet files to clear all shipped snippets.
3) You can also redefine g:UltiSnipsSnippetDirectories and store your snippets in a directory that is not named UltiSnips to avoid sourcing the shipped snippets in the first place. See the docs for this.

Changed in ultisnips:
status: New → Confirmed
importance: Undecided → Wishlist
milestone: none → 2.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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