-
-
Notifications
You must be signed in to change notification settings - Fork 307
Description
Is your feature request related to a problem? Please describe.
I don't know how Neogit uses default highlight groups and its settings to create its own ones, but some default colorschemes are literally unusable (see habamax, retrobox). Some others work nice, where text is at least readable (i.e default, desert).
Describe the solution you'd like
While I understand that, in the likely case the issue is not intrinsic to Neogit itself, or the way it creates its own highlight groups, then I think that having a way to pick a preferred colorscheme to be used when in a Neogit context would be a nice option, instead of being forced to manually modify HLGs.
For example, I like the appearance with the default colorscheme, minimal but readable.
Indeed, the previous colorscheme will be reset once exiting Neogit.
I do admit I don't know exactly how much changing the colorscheme is an expensive task to do, but I guess the change can be done in parallel while the Neogit window is being computed, before the actual draw.
Same goes for the exit step, which might be faster than the load, but yet.
However, I think mason does something similar for its floating window.
Describe alternatives you've considered
The only alternative is to manually define custom highlight groups properties, which I don't think is very elegant, although functional for those who want full control.