On Thu, Nov 8, 2012 at 3:22 PM, Chet Ramey <chet.ra...@case.edu> wrote: >> 2) remove duplicates in HISTFILE also, not just in current history in >> memory, we can say this a deep dedup? it only run deep dedup when >> HC_ERASEDUPS set, > > I'd rather see this done (and have adapted your previous code submission to > do so) in a separate program that links with the history library and can > operate on arbitrary history files outside of bash. There are applications > besides bash that use readline, save history, and could benefit.
while the current erasedups logic is implemented in bash, I want this also get into bash, we may define another control like "erasedupsinfile" if the user set that we will erase dups in history file as well HISTCONTROL=ignorespace:ignoredups:erasedups:erasedupsinfile if we contribute a binary to dedup in history file, we still need the logic to call it automatically, depending some similar control variable is set
