Activity log for bug #106526

Date Who What changed Old value New value Message
2007-04-14 11:44:50 Nicolò Chieffo bug added bug
2007-04-14 17:11:37 C de-Avillez bash: status Unconfirmed Needs Info
2007-04-14 17:11:37 C de-Avillez bash: importance Undecided Medium
2007-04-14 17:11:37 C de-Avillez bash: statusexplanation Please verify your environment variables; from the man page for bash: HISTCONTROL 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 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 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.
2007-04-14 17:11:37 C de-Avillez bash: assignee hggdh2
2007-04-14 23:02:20 C de-Avillez bash: status Needs Info Rejected
2007-04-14 23:02:20 C de-Avillez bash: assignee hggdh2
2007-04-14 23:02:20 C de-Avillez bash: statusexplanation Please verify your environment variables; from the man page for bash: HISTCONTROL 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 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 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. mc is midnight commander. Yes, it is certainly not like what it was. Anyways... not a bug.
2013-09-12 16:17:47 Jan Groenewald bug added subscriber AIMS