On 15 Dec 2012, at 9:43, Johannes Deutsch wrote:
On Fri, 14 Dec 2012 20:24:27 +0100
"Niels Kobschätzki" <[email protected]> wrote:
<snip vundle throws errors when installing Ultisnips which seem to have
nothing to do with Ultisnips
Any ideas what I can do about it or at least get to know where the
command and function exist as well?
When I received errors like the ones you've described the case was
always, that vim sourced the corresponding files (in your case
bclose.vim, remoteOpen.vim) more than once.
But why don't I get that error everytime vim starts but only when I
issue BundleInstall?
I suspect, that the reason for your errors is the same. That is
supported by the fact that vim mourns about the existence of s:Kwbd.
But actually, the 's:' prefix says that the function is scoped to the
file where the function is located. So the only way that another
function conflicts bclose.vim/s:Kwbd is a function with the same name
in the same file i.e. sourcing the file twice.
So i'm quite sure, that UltiSnips isn't the reason for your errors.
The easiest way to solve the error would be to do what vim suggest.
Add
the '!' to the command and the function.
Did that - threw other errors (undefined functions and stuff)
Another possibility is to study the output of ':scriptnames'.
I didn't see any suspicious there
Niels
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
