-
Notifications
You must be signed in to change notification settings - Fork 8
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
Allow to start vimade disabled #25
Comments
Added some documentation and cleaned up some logic to support Vimade disabled at startup --
I think for the issue that you were experiencing, this shouldn't be necessary anymore, the garbage characters were likely being caused by detecttermcolors, which I've now set to disabled by default. |
Hmm, I tried with |
Strange -- will need more info, what is the indication that vimade is still enabled -- are the buffers still fading or something else? Also can you verify that g:vimade_running is still 0 after vim has loaded? |
Well I could have done that in the first place… Didn't think about it, sorry. Now I have tried around a bit and found the following. I am using the Volt package manager for vim 8 where I can define configuration settings to be done per package before a package is loaded or after a package is loaded. I have played around with setting In all three cases the value of So it seems that the setting of |
Will take a look as soon as I get a chance -- do you have a minimal vimrc that I can use? If not I'll try to recreate with volt. |
I tried to provide a minimal vimrc to reproduce it, but it doesn't happen there. So I tried using volt, but also with no other plugins and an empty .vimrc and it still doesn't happen. So there seems to be a conflicting plugin or setting in my vimrc. |
It seems that there is no option to start vimade disabled and having to activate it via VimadeEnable.
I think such an option could help to work around problems like #24.
The text was updated successfully, but these errors were encountered: