Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
vim-command-loop.patch from Debian #74
I've looked at Debian's patches to exuberant-ctags, and the following might be interesting for you:
More patches are available at http://anonscm.debian.org/cgit/users/cjwatson/exuberant-ctags.git/tree/debian/patches/, but only http://anonscm.debian.org/cgit/users/cjwatson/exuberant-ctags.git/tree/debian/patches/python-disable-imports.patch seems to be missing, and I'm not sure if it's a good one.
I tried the patch; and I got a question.
In your report at exuberant Bugs tracker, following example input is introduced:
In this case what is exepcted as ctags output?
'foo input.vim /&comand'foo'$/;" c
A single quote at the head of line is expected?
The expected output would be "none" probably, because this isn't a valid command name (according to Colin, who fixed the bug): https://bugs.launchpad.net/ubuntu/+source/exuberant-ctags/+bug/736367/comments/1
added a commit
Sep 20, 2014
I've meant that, but am not sure. Because the command name is invalid (
Currently (using the patch) parses it as
vim-lustyexplorer uses it in its Ruby code (https://github.com/sjbach/lusty/blob/master/autoload/lustyexplorer.vim#L161), which is used to call the command, but not to define it:
The main issue here is maybe that the parser for vim should ignore any
added a commit
Sep 22, 2014
referenced this issue
Sep 23, 2014
Yes, only in the outcome of the unit test(vim-command.d/input.vim).