Since zsh is the default for a standard Manjaro (Gnome) user, this seems like a configuration flaw. But maybe this is only me.
Since the dawn of time (or the horrid user experience of the commercial *NIXs), I have used hash/# to comment out commands. This is handy to type out a command, then press ^A/# to comment the whole command out, hit enter and come back to it.
I’ve never known Bourne, Bash, or any other shell to act any other way. I only learned about the INTERACTIVE_COMMENTS option after Manjaro. I see OSX users that also use zsh with the same option disabled.
Of course I can easily change this for myself. But let’s not be like Apple! We need our hash!
My reply got lost a few days ago, in that incident.
I just wanted to understand the reasoning of the default configuration of zsh. In the first reply, you edited in:
So that one word made sense on the reasoning, histchar was the part I was missing.
echo $histchars 127 ✘
There’s a few ways of changing this. (Of course going back to Bash would!) I was just using the setopt interactivecomments option. I just couldn’t understand why this wasn’t the default, like it is in Bash. Everything else I’ve liked about zsh, but I was confused on why they would repurpose that character here.
Since even in ksh over 3 decades ago, I could just set -o vi, then type out drafts of long commands, then use the hash to comment, and come back them. Every other shell I’ve used has worked this way, and that ^A/# two key combo, I use all too much without even thinking. I thought this was a common thing people did, but as I said, maybe it’s just me.