-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E605: Exception not caught: NERDTree.InvalidArgumentsError #265
Comments
I am also experiencing the same problem (although my use-case is different). |
Also reported at #256. @scrooloose: you alive man? Any friends of him know if he's ok? The last twitter post I could find on him was over a year ago, the blog linked to on gh is even later. |
@tony His last public commit on GitHub was this Jan. Maybe he doesn't tweet or blog anymore. https://github.com/PlayMob/playmob_home_locomotive_engine/commits?author=scrooloose |
Unfortunatelly, he does not support this product.. |
I sent him a mail. My gut tell me he's working and even on gh, just not with public commits. On that note @PlayMob would know for sure. They should consider sponsoring him some time for his plugs |
I think the collaborators are needed like Vundle. |
Wait what?! Vundle isn't being supported? I just moved everything from Pathogen for nothing?! 😞 |
No. Vundle is supported by collaborators. But the original author have not much time to support. |
In snipMate, the development is chaotic. A lot of forks confuse users. |
Experiencing the same problem. However, if you
It doesn't complain anymore. Probably one of the ownership might have mixed up. |
I can't reproduce this. Is this still happening for anyone else? |
I likely either
i'm ok with closing unless it flairs up again |
This error sometimes occurs when I save the markdown file |
1,Create file E:\test.c 2,Put this to vimrc
3,Start gvim I'm using gvim 8.2 64bit on window7. |
Steps to reproduce
My
.vimrc
:Execute:
From within vim:
The following error is thrown:
The text was updated successfully, but these errors were encountered: