I'ma stop you there: more than one brain exists, and they don't all behave the same.
> using `less` is always painful for me
`less -R` preserves colours.
I'ma stop you there: more than one brain exists, and they don't all behave the same.
> using `less` is always painful for me
`less -R` preserves colours.
Let me stop you there then: From that perspective viewing syntax highlighting as childish is normal for some brains. Empathy goes both ways.
> `less -R` preserves colours.
Preserves but doesn't magically add.
highlight -O ansi file.txt | less -R
The Python syntax in Debian's highlight isn't quite right, but feel free to use your favourite syntax highlighter. That's what the UNIX philosophy is all about!And just to counter your suggestion I often use `less` in environments where I am unable to install anything (or it doesn't make much sense to, like a Docker container).
You're trying to apply technical solutions to a problem where I was trying to highlight (pun intended) the cognitive function of a mind trained to read code without syntax highlighting vs one reliant on it (like my own). It doesn't matter if you can solve this particular one. Nor does it change the fact that someone who is used to seeing monochrome code might view colored code as playful and/or childish (like seeing colored piano keys).
I would argue that it makes sense to install any tools that would help you, in your development environment, and that it makes little sense to ship an entire OS in your Docker container, so you shouldn't be in a situation where you have `less` and no syntax highlighting – but I'd argue with a lot of aspects of Docker-driven development, and I've learned there's little point.