[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU History 6.3

From: frederik
Subject: Re: GNU History 6.3
Date: Mon, 25 May 2020 05:46:51 -0700

I think not saving lines that start with space is intentional. Here is some 
information from the Bash manual page:

       HISTCONTROL A colon-separated list of values controlling how commands 
are saved on the history list. If the list of values includes ig- norespace, 
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.

On Sun, May 24, 2020 at 05:10:28PM -0700, Marshall Lake wrote:

Re:  GNU History 6.3

The GNU History library doesn't seem to pick up commands from the CLI that do not start in column 1 (even though they execute fine).

Is this the way it should be?

Marshall Lake -- address@hidden -- http://www.mlake.net

reply via email to

[Prev in Thread] Current Thread [Next in Thread]