4 ms·

> But then, proposes to not highlight keywords at all, so misspelling "return" would still be impossible to quickly scan for visually! Yeah I generally want th

> But then, proposes to not highlight keywords at all, so misspelling "return" would still be impossible to quickly scan for visually! Yeah I generally want the opposite. I want keywords to be the thing being highlighted. I also really dislike overly colorful themes, and I prefer light mode (dark mode is far too hard on my eyes, oddly enough I have to strain to focus or it's fuzzy). But the author's alabaster theme still highlights the wrong things and is inconsistent. public async Task<byte[]> SomeMethodName(Type param, Type param) results in Task, SomeMethodName, and BOTh the data type and parameter name being highlighted. If highlighting isn't for keywords, why is Task and the data types highlighted? likewise var result = await SomeMethodName(param, param); has result and SomeMethodName highlighted and I generally want the opposite, I want the PL's keywords highlighted and nothing else.

tasuki 1y ago
> prefer light mode I prefer dark mode (precisely for the garish colors, sorry), but been using light mode... because it's hard to make everything use dark mode! When my terminal was dark, the eg some docs in the browser were light, switching back and forth was quite painful. Yes, it's super simple for websites to detect the preferred color scheme with @media (prefers-color-scheme: dark) {}, yet most (such as this one) don't. I could use some hacks, but then I'm in for a world of pain. So I just use light theme everywhere and it's ok(ish).
- queenkjuul 1y ago
  I was like this for a long time, but Dark Reader for Firefox and the default OS dark modes are good enough now I'd rather once in a blue moon fiddle with Dark Reader to correct a bad auto-color-assignment than put up with light mode in my browser and terminal overall. Just a thought. Until the last ~2 years, with win11, latest Linux desktops, and recent macOS all facilitating the change (if i couldn't do it everywhere i might still not do it, y'know? But they all actually work pretty reliably now)
- jezek2 1y ago
  > When my terminal was dark, the eg some docs in the browser were light, switching back and forth was quite painful. I do this all the time (even at night without lights) with no problem at all. The key is to have properly set brightness/contrast on your monitor and gamma correction. It can achieved by setting the brightness to a minimum (and use the contrast setting to go even lower, or even combine it with GPU settings in addition to monitor settings). It is also important to set a proper gamma correction so that darker/lighter levels don't have too big contrast. The gamma correction needed can be measured by comparing the apparent thickness of antialiased text in black-on-white vs white-on-black color combinations that you toggle between. Once it is the same you get the right value. For example it's 1.3 on my LCD.

tasuki 1y ago

> prefer light mode I prefer dark mode (precisely for the garish colors, sorry), but been using light mode... because it's hard to make everything use dark mode! When my terminal was dark, the eg some docs in the browser were light, switching back and forth was quite painful. Yes, it's super simple for websites to detect the preferred color scheme with @media (prefers-color-scheme: dark) {}, yet most (such as this one) don't. I could use some hacks, but then I'm in for a world of pain. So I just use light theme everywhere and it's ok(ish).

queenkjuul 1y ago
I was like this for a long time, but Dark Reader for Firefox and the default OS dark modes are good enough now I'd rather once in a blue moon fiddle with Dark Reader to correct a bad auto-color-assignment than put up with light mode in my browser and terminal overall. Just a thought. Until the last ~2 years, with win11, latest Linux desktops, and recent macOS all facilitating the change (if i couldn't do it everywhere i might still not do it, y'know? But they all actually work pretty reliably now)
jezek2 1y ago
> When my terminal was dark, the eg some docs in the browser were light, switching back and forth was quite painful. I do this all the time (even at night without lights) with no problem at all. The key is to have properly set brightness/contrast on your monitor and gamma correction. It can achieved by setting the brightness to a minimum (and use the contrast setting to go even lower, or even combine it with GPU settings in addition to monitor settings). It is also important to set a proper gamma correction so that darker/lighter levels don't have too big contrast. The gamma correction needed can be measured by comparing the apparent thickness of antialiased text in black-on-white vs white-on-black color combinations that you toggle between. Once it is the same you get the right value. For example it's 1.3 on my LCD.