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

Do you use this on Eink? #5

Open
generalredneck opened this issue Feb 9, 2024 · 0 comments
Open

Do you use this on Eink? #5

generalredneck opened this issue Feb 9, 2024 · 0 comments

Comments

@generalredneck
Copy link
Contributor

Hey there,
First, Thank you for putting this theme together. I use this theme explicitly on my Dasung 25.3 paperlike U. There are several difficulties I've found when using it as my daily driver though and thought it would be good to collaborate with you on some of these and discuss how you work with your own theme.

20240209_124908-min

I have to use Graphic mode, Text mode just blacks stuff out and the greys make unclear text, which I'm ok with, I work in graphics mode most of the time. Video mode's quality is just too bad.

Here are a list of things I've noticed:

  • Terminal's color contrast are just bad. You can see the table above and how the various colors look on eink. Here's what they would look like on color. We should probably do some testing around these values to optimize for Eink
    image

  • The inline blames are just barely legible, they are so faint. I can increase the contrast but that affects with visibility of other things.

  • The popups are all that mid Grey color. It makes it hard to read any of the suggestions. I recommend we have a dark bold border and white background as that default to make that all stand out. The example shows a commit in the popup with my recent diff changes which I didn't know would be part of that... Those colors I chose for Diffs don't work on the grey at all. The popup doesn't show JUST commits though. It's used for code documentation too.

  • The tabs in the workspace are various shades. So if you have a inactive tag on an inactive pane, you have a super dark tab that you just can't read the filename on very well.

  • I had to set custom debugging colors, because the defaults are SUPER LIGHT all the way across the board... Except when you hover over an item. I have some starting colors as

           "debugTokenExpression.boolean": "#000000",
           "debugTokenExpression.name": "#333333",
           "debugTokenExpression.number": "#000000",
           "debugTokenExpression.string": "#888888",
           "debugTokenExpression.value": "#888888",
    

    20240209_130907-min

  • The highlighting on the left hand explorer bar makes it where nearly can't see the icon you have selected.

  • The buttons in the Extensions store that say "Install" or "Reload" are just pretty much black.

  • The options button is missing the top of it's border.
    20240209_131636-min

  • highlighting in the text editor is a little dark. Maybe there is a better treatment?

The script I used for the bash colors is as follows:

#!/bin/bash
#
#   This file echoes a bunch of color codes to the
#   terminal to demonstrate what's available.  Each
#   line is the color code of one forground color,
#   out of 17 (default + 16 escapes), followed by a
#   test use of that color on all nine background
#   colors (default + 8 escapes).
#
#   Copied from http://tldp.org/HOWTO/Bash-Prompt-HOWTO/x329.html

T='gYw'   # The test text

echo -e "\n                 40m     41m     42m     43m\
     44m     45m     46m     47m";

for FGs in '    m' '   1m' '  30m' '1;30m' '  31m' '1;31m' '  32m' \
           '1;32m' '  33m' '1;33m' '  34m' '1;34m' '  35m' '1;35m' \
           '  36m' '1;36m' '  37m' '1;37m';
  do FG=${FGs// /}
  echo -en " $FGs \033[$FG  $T  "
  for BG in 40m 41m 42m 43m 44m 45m 46m 47m;
    do echo -en "$EINS \033[$FG\033[$BG  $T  \033[0m";
  done
  echo;
done
echo
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

No branches or pull requests

1 participant