On 1/3/14, 5:35 PM, David Korn wrote:
> Since all HISTCONTROL does is eliminate immediate duplicates or no keep
> commands that start with a space, I don't know why this can't be the
> default behavior.
HISTCONTROL is the original bash history control mechanism and is intended,
as you noted, to handle the common cases simply. If you're going to
implement something, take a look at HISTIGNORE.
> Ignoring failed commands seems like a bad idea. Failed command often occur
> because of a typo and in this case I want to edit the failed command.
HISTIGNORE doesn't pay attention to whether or not a command fails, only
its content.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/
_______________________________________________
ast-users mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-users
