Skip to content
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

default color bottom line / file info #878

Closed
grammoboy2 opened this issue Jul 21, 2022 · 2 comments · Fixed by #1288
Closed

default color bottom line / file info #878

grammoboy2 opened this issue Jul 21, 2022 · 2 comments · Fixed by #1288

Comments

@grammoboy2
Copy link

default color bottom line / file info is white. In nnn it's blue, in Ranger it starts with a different color then white (purple here). A different color for the bottom line, makes reading more pleasant.

@camoz
Copy link

camoz commented Nov 11, 2022

I disagree: white is a safe default for readability. Reason: Many terminal programs only use 8/16 colors, as a result many users have tweaked their terminal colors. This often results in not-ideal or poor readability of some color combinations. nnn uses normal blue on black, which is not ideal either.

Example, from top to bottom:

  • nnn
  • lf
  • ranger
  • ls -lh

slurp_2022-11-11_022044

FWIW I like ranger's output the most. Selective use of colors (similar to syntax highlighting) makes is more readable. Also, its output is very similar to ls -lh, which many people are familiar with.

There is no point in changing the color for the complete text, IMO. The statusline is already simple to read/locate since it's located at the bottom of the screen.

Edit: The above shows lf release 27, not sure why owner and count are not displayed, I see it should via 60d6119.

@latipun7
Copy link

latipun7 commented Nov 14, 2022

I like ranger format too. I hope statusline can be configured, something like statusfmt.

PS: I think owner and count would be fixed in the next release thru #829, which not in the release yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants