|
From: Daniel J S. <dan...@ie...> - 2007-06-06 21:48:43
|
Petr Mikulik wrote: >>OK, I think you will like this new patch (#1729825). Type >> >> help history >> help set history > > > Yes, it works. > > >>Here is something really neat, and nothing kludge-like about it from the >>perspective of readline. When "set history condensed" is active, the up/down >>arrows will now also scan through only unique history entries, like you want >>Petr. Here is the elegant way to do it. Simply write a routine like > > > Please add the to skip duplicated entries with the up-arrow. It does not > make sense to press up so many times, even though many same lines are in > history, does it? After one sets set history condensed the up arrow should only sequence through unique commands. That is the way it works here. > > BTW, bash does not store duplicated entries (try several times to type "ls" > and then "history"). Do you need it for gnuplot becase of possible > k=k+1 > commands? For commands like hist !87 which will execute the 87th line on the history stack. If we keep moving the stack around "hist !87" might mean something different in the future. Also, when saving the history of commands to a file, it is an exact record of what was typed. Dan |