They meant that you'd get the same message no matter what unrecognized option you use. So it's not like they added a specific check that if you type in -h they will give you the message, but instead you get the same message for any unrecognized option.
The thing in the OP only occurs if you type exit, so they specifically added that message to be shown when the interpreter clearly knows what you want, but you just didn't say it exactly right.
And what's TCP/IP?
Looks like Mercurial can change the history just fine using the hg command. You just need to enable it first.
https://book.mercurial-scm.org/read/changing-history.html
Git can also be configured to disable history rewrites.
https://stackoverflow.com/questions/2085871/strategy-for-preventing-or-catching-git-history-rewrite
So the difference between git and hg really just comes down to the defaults.
I got weirdly invested in this, and by the end I was kinda happy that it was "just" a bug in the tooling and not anything actually malicious.
Especially that + and - act differently. If + does string concattenation, - should also do some string action or throw an error in this situation.
Thanks for the warning. I am currently running Fedora (because "it just works") and I'm drowning in bugs and incompatibilities.
I was considering Bazzite because of all the recommendations, but considering my luck (and probably my hardware combination) I'd probably end up just like you described.
On Reddit you'd be banned for that statement. Good that this is not Reddit.
Multiple reasons can be true at once.
It's not the client, it's markup.
Nice, a relevant xkcd that I didn't guess before clicking the link! Well done!
Does gtfo() then work as expected?