Closed mortezadadgar closed 1 year ago
I don't understand the problem or the suggested solution.
OK let me try one more time: for example this is where you hardcoded color for untracked: https://github.com/romkatv/gitstatus/blob/38d35b95926e09d07b8cf78edade7cee7a9a1dcf/gitstatus.prompt.zsh#L39 I don't understand the syntax but to me it looks like a color code this seems to the color used by terminal https://github.com/romkatv/gitstatus/blob/38d35b95926e09d07b8cf78edade7cee7a9a1dcf/gitstatus.prompt.sh#L38 so no matter what color I have configured in my terminal color it will be that
to me gitstatus uses 8-bit colors for zsh and 256 colors for other shell
Your screenshot isn't using this code.
Can you describe what you do, what you expect and what you observe?
I expect 256 colors to be used for zsh
Your screenshot isn't using this code.
I sourced ~/git/gitstatus/gitstatus.prompt.zsh
sorry I meant base16 colors not 256...
See docs starting from here: https://github.com/romkatv/gitstatus/blob/38d35b95926e09d07b8cf78edade7cee7a9a1dcf/README.md?plain=1#L93
Alternatively, use powerlevel10k.
yeah good to know it can be configured but I think having base16 terminal colors being used as default is closer to what users are using in their terminals yeah I can change them to base16 I guess but why would be there predifined colors is source if everybody is going to change them anyway? I'm just suggesting to use sane-defaults colors
Changing the default colors will change the prompt of existing users. That's a no go.
Besides, it's questionable whether the lower 16 colors are preferred. Powerlevel10k has a choice and the vast majority of users selects high-numbered colors.
Hey, Currently gitstatus uses custom colors which might be not the one the users are using in their terminal: for example untracked foreground is not what i use in my terminal as you can use it differ from path color in any case it's better to use terminal colors as they represents colors used by users instead of hardcoding it in source code