A user should have the possibility to overwrite DMD's default color scheme, because
- there are some issues with it (e.g. 18348)
- people have different tastes
Ideas:
- color-XXX flags
- dmd.conf
Comment #1 by destructionator — 2018-02-07T16:50:24Z
I'd argue they kinda can by doing a palette swap in their console/terminal emulator... (the real WTF is most those ship with barely usable default palettes! that's one of the reasons why i wrote my own, not only to change the palette but to make it do adaptive contrast...)
Comment #2 by greensunny12 — 2018-02-07T17:02:00Z
> I'd argue they kinda can by doing a palette swap in their console/terminal emulator.
Note that not all terminals are equal, my terminal has some issues with boldness:
https://github.com/dlang/dmd/pull/7822
Also, there are and always will be personal preferences.
Should dmd really use boldness for the keywords? Why not white? Or pink? etc.
This is highly subjective and I don't see any reason why it shouldn't be allowed.
Comment #3 by destructionator — 2018-02-07T17:06:48Z
It's just more configuration that has to be coded, tested, documented, and actually used by the end user. Whereas knowing how to fix up your terminal palette will just work across all programs.
I remain of the opinion that this syntax highlighting is a mistake anyway, even if the implementation was free (which it isn't): it adds nothing of value and has an opportunity cost of watering down the potential of using careful color output in some other way later, but if it is here, even if it is configurable, the default has to be reasonable in 99% of cases since only 1% are likely to even be aware of such an option, much less actually set it.
So I'm not against adding the option per se, but I do caution against using the option to paper over the deficiencies of the default.
Comment #4 by robert.schadek — 2024-12-13T18:56:54Z