leading space in command line won't save command in history

[anddam]

Typing a command with a leading space prevents the command from being saved in history.

To reproduce print out the history file content, either using cat or tail -f and then run

echo "foo"
 echo "bar"

the first line is added to the file while the second isn't.
This can be reproduced with 2.0.0 and 2.1.0 on OS X and Arch Linux.

[ridiculousfish]

Yes, this is a feature common across other shells. bash has it as HISTCONTROL=ignorespace. See #615

[anddam]

Ah, now I see it in Documentation > Command line editor:

Prefixing the commandline with a space will prevent the entire line from being stored in the history.

a classic case of "it's a feature, not a bug".

It'd be still nice to be able to turn the feature off as it's mentioned about in #615.

This ticket can be closed.