-
Notifications
You must be signed in to change notification settings - Fork 401
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
feature: How to cancel the theme loading when the plugin is automatically installed #713
Comments
|
Is an issue for me as well Just started trying out |
well if you comment that part out there won't be anything overwritten |
I tried commenting the subject field but it didn't work. I need to automatically install the plug-in function, so I can't annotate the whole thing. |
I have no clue what you're talking about |
It doesn't work |
That colorscheme is only loaded while installing. You should load our own colorscheme after that |
Hi @folke, shouldn't the default behaviour be to not load/override a colour scheme? Isn't the plugin forcing users to define a color scheme when they'd want to use only the package manager? Is there a reason why this behaviour is marked "not planned" |
This gives the option to not override default colorscheme during plugin installation by using the configuration: ``` { install = { colorscheme = {}, }, } ``` If the user specifies a scheme or keeps the default, we will fall back to 'habamax' as before.
Remove default to habamax to work correctly with default colorscheme (folke#713)
Did you check the docs?
Is your feature request related to a problem? Please describe.
When I update the plugin list and restart nvim, the plugin installation is automatically triggered, and the theme is also automatically loaded, disrupting my original color scheme
Describe the solution you'd like
Optional cancel theme loading operation
Describe alternatives you've considered
I can't find any operation to cancel the automatic loading theme in the document, and the option to automatically load the theme list has been blocked by my comment
Additional context
No response
The text was updated successfully, but these errors were encountered: