Closed aaravind100 closed 1 year ago
Hey Ajith.
Chasing the perfect color for each theme is a Sisyphean task. editorCodeLens.foreground
was chosen because it is the color used when showing information about the code in the editor. It should be possible to override this color in your settings.
I understand, thanks for the suggestions :smile:
@Sertion Could it be possible to change which colour the inline blame references? E.g. to point it at the theme's comment colour variable instead? The comments are usually more subtle than the foreground text. Instead of hardcoding foreground vs comment colour, perhaps leave it up to the user to define which colour variable to use? Thanks for Git Blame!
The comments are usually more subtle than the foreground text. Instead of hardcoding foreground vs comment colour, perhaps leave it up to the user to define which colour variable to use? Thanks for Git Blame!
Sadly there is no good way of allowing a "color" as a setting and writing something to detect what random color-like string the extension has gotten through a setting is not something I'm interested in exploring.
Implemented in #168.
Thank you!!
FYI for anyone reading this, we should add this to settings.json to use a custom color.
"workbench.colorCustomizations": {
"gitblame.inlineMessage": "<hex color code>"
}
Hey @Sertion , Good day!!
Would a more subtle color for the inline blame make sense or maybe an option to set a custom color code?
Presently the color is set by the
editorCodeLens.foreground
here. This looks good with the default theme, but looks prominent in some themes, rose pine for example.editorWhitespace.foreground
maybe?This is indeed trying to emulate the style from gitlens, which has become quite bloated lately :sweat_smile:
I'd be happy to submit a pr for this.