> with red colored text that is difficult to see on a black console. Thanks for your honest feedback. It's only errors that appear in red and you can disable t

> with red colored text that is difficult to see on a black console. Thanks for your honest feedback. It's only errors that appear in red and you can disable that feature if you want[1]. However it's pretty standard these days for DevOps tools to output errors in red but I appreciate that is still not to everyone's tastes. [1] https://murex.rocks/docs/user-guide/interactive-shell.html https://murex.rocks/docs/user-guide/interactive-shell.html It should also be noted that I'm honouring the terminal emulators colour palette. So if a colour isn't readable then it's the terminal emulator you're running that has caused that issue. Personally I recommend the Solarized colour themes because all 16 colours are equally readable but your preferences might differ. > There is little incentive to switch and lots of incentive to continue toward mastery of the ubiquitous shell, the one I have to use on POSIX-like OS, on computer of all sizes, like it or not. I do get that sentiment but more and more these days most of the console work is done on your local machine and you rarely SSH onto remote hosts (some orgs even go as far as to disable SSH access entirely since everything should be managed via Ansible/Puppet/Chef/SSM/etc). The problem murex attempts to solve is to be a better shell for local development / DevOps tooling. There's no point trying to get murex pushed as a default shell on servers because no security team would authorise it. But for local tooling there are still a lot of gains to be made. This is why you'll see features like errors highlighted in red and spelling errors underlined. murex takes as many cues from IDEs (local development) as it does from POSIX-shells.