history not saved if a command begins with a space
Bug #106526 reported by
Nicolò Chieffo
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: bash
I'm running feisty (up to date) and I noticed that if I put a space before the command, it is not saved in the history:
it is not in .bash_histiry and it is not shown when using the up arrow.
I think this bug is here since an update that enabled the mouse wheel in applications like vim
To post a comment you must log in.
Please verify your environment variables; from the man page for bash:
HISTCONTROL
previous lines matching the current line to be removed from the history list before that line is
saved. Any value not in the above list is ignored. If HISTCONTROL is unset, or does not include a
A colon-separated list of values controlling how commands are saved on the history list. If the list
of values includes ignorespace, lines which begin with a space character are not saved in the history
list. A value of ignoredups causes lines matching the previous history entry to not be saved. A
value of ignoreboth is shorthand for ignorespace and ignoredups. A value of erasedups causes all
valid value, all lines read by the shell parser are saved on the history list, subject to the value
of HISTIGNORE. The second and subsequent lines of a multi-line compound command are not tested, and
are added to the history regardless of the value of HISTCONTROL.