Subject: Re: bug#30466: 25.3; Eshell: Ignore all duplicates when ignoredups is non-nil

From: Glenn Morris <[email-masked]>
Date: Thu, 15 Feb 2018 12:24:09 -0500

Pierre Neidhardt wrote:

> This does not prevent Eshell from cluttering the history with the same
> commands as long as they are not consecutive (e.g. A, B, A, B...).
>
> I find more useful to always remove the duplicate entry back to the
> first position.  It makes the history much lighter and much easier to
> browse/filter.

In terms of bash HISTCONTROL, this is the difference between
"ignoredups" and "erasedups".

Ref eg https://www.gnu.org/s/bash/manual/html_node/Bash-Variables.html#index-HISTCONTROL