bash doesn't record commands that start by whitespace

[bingmatv]

bash doesn't record commands that start by whitespace

[ysthakur]

Hmm, could you post your config and add what you did in the terminal and what you saw? I haven't made any changes related this in my own config and if I start a line with a space, it's not recorded in history. This has been true for several versions now.

[NotTheDr01ds]

Yes, this was implemented in #9371 (and the corresponding Reedline nushell/reedline#566) just over a year ago.

However, there might be a slight bug in it depending on how you view things, and perhaps this is what you are seeing?

The "bug" is that the most recent command appears to be cached in memory regardless of whether it is preceded by a space or not. If you hit ↑ (Up arrow) immediately after typing a space-suppressed command, that command will appear on the commandline.

However, note that it is never persisted to the history file, and it will disappear from the up-arrow history as soon as the next command is entered.

It's tough to even classify this as a security risk, though, since in that scenario the previous command is going to appear on your screen anyway. Even a Ctrl+L to clear the screen is going to leave it in the scrollback for your terminal app. You'd need to enter a clear --all in order to truly remove it, in which case it would also no longer be available via up-arrow (since the clear command would have overwritten it).