-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Vaffle and projectionist interfere with one another #56
Comments
I use the projectionist vim plugin (https://github.com/tpope/vim-projectionist). When I attempt to use :Vaffle an exception occurs:
When in autoload/vaffle/buffer.vim the 'file' command is used to rename the buffer this triggers an autocommand in projectionist that attempts to detect the type of the buffer. Beyond that I'm unclear on exactly what is happening. I will continue to look at it but I don't know that I'll resolve this issue on my own. To replicate simply install projectionist and attempt to run Vaffle. |
The most radical change that will work is to use 'noautocmd' for the line that runs 'file'. This seems like using a nuclear bomb to kill a fly. autoload/vaffle/buffer.vim:
|
I can
in my config and this will ignore anything with the namespace 'vaffle'. This appears to be undocumented but is in the projectionist code. It also keeps projectionist and vaffle from interfering with one another. |
The actual cause of the problem appears to be projectionist attempting to execute "runtime! autoload/vaffle.vim" from within s:load() in the plugin/projectionist.vim code. I haven't wrapped my head around all that projectionist is doing. For now I think I'm going to just do the thing I mention in the above comment. |
@WhoIsSethDaniel does using |
I've been using it without issue for months. Doesn't remove any features as far as I can tell. |
No description provided.
The text was updated successfully, but these errors were encountered: