Kevin Matthes

Okay, the colour is definitely unused: removing the underscore from `_light_background` in `zee/src/components/theme/mod.rs`, line 199, causes the compiler to generate warnings. Hence, this is the place where the colour `base07`...

The separators are the bug, not their vanishing. The problem seems to be something about the style `position_in_file` which is applied to the repository name and the reading progress.

The "separators" are spaces which are not coloured in the configured background colour. If one switches to `is_not_modified`, the bug does not appear anymore but it does continue to appear...

#80 tries to solve the problem by using a different background colour. And indeed, this solves the problem. But when increasing the number of spaces before the file size, this...

There is a protected area at the left end of the status bar, 18 characters in size. When using `lighter_background` and `dark_foreground`, the spaces will fetch indeed `lighter_background` only within...

The reason why #80 achieves a partial solution is that one assign *literally* any colour to the background of `position_in_file` ***except one which equals `base01`.*** *Even one RGB step in...

After all, the status bar could just have a different colour than the current line, right? One option to fix this issue would be to assign `base01` solely to the...

Another option is rendering the affected fields of the status bar with `bold` instead of `normal`. This would be the minimal invasive version.

#85 is a suggestion how this mechanism might be introduced. I am looking forward for feedback and wishes for further common second suffixes in case I should have forgot some.

Yes, this is a very interesting feature, thank you for your enhancement! I would like to suggest to focus on the first option to outsource the mode definition to an...