vim/UltiSnips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Removed no longer planned TODOs

Browse Source
This commit is contained in:
Holger Rapp 2014-03-05 19:04:16 +01:00
parent 147df653ae
commit a800b51e0e
2 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pythonx/UltiSnips/snippet/source/file/_base.py
View File

@ -94,8 +94,6 @@ class SnippetFileSource(SnippetSource):
_vim.escape(filename)) _vim.escape(filename))
raise SnippetSyntaxError(filename, line_index, msg) raise SnippetSyntaxError(filename, line_index, msg)
elif event == "clearsnippets": elif event == "clearsnippets":
# TODO(sirver): clear snippets should clear for
# more sources, not only ultisnips files.
triggers, = data triggers, = data
self._snippets[ft].clear_snippets(triggers) self._snippets[ft].clear_snippets(triggers)
elif event == "extends": elif event == "extends":

8
pythonx/UltiSnips/snippet/source/file/snipmate.py
View File

@ -12,14 +12,6 @@ from UltiSnips.snippet.source.file._base import SnippetFileSource
from UltiSnips.snippet.source.file._common import handle_extends from UltiSnips.snippet.source.file._common import handle_extends
from UltiSnips.text import LineIterator, head_tail from UltiSnips.text import LineIterator, head_tail
# TODO(sirver): garbas/snipMate supports guard expressions. I could not figure
# out how the work though and therefore did not implement them. They should be
# fairly straightforward to add if I understand their purpose correctly.
# TODO(sirver): the snipMate docs state that a snippet without description gets
# overwritten by one with the same trigger but without description. I find this
# silly and will only implement if people start complaining.
def _splitall(path): def _splitall(path):
"""Split 'path' into all its components.""" """Split 'path' into all its components."""
# From http://my.safaribooksonline.com/book/programming/ # From http://my.safaribooksonline.com/book/programming/