tag 661669 fixed-upstream thanks On Wed, Feb 29 2012, Raf Czlonka wrote:
> I can't quite remember when it stopped working, but the command history
> in prompt (Mod4+r) always appeared in th order they had been executed,
> i.e. if I started luakit, then uzbl, then luakit again, I would see
> luakit, after pressing (Mod4+r) and up arrow, as it was the last command
> I executed; now I will see uzbl, even though I run luakit after it.
>
> The problem becomes more apparent with dozens of commands in the history
> when running a command, which has been executed 5 commands before, twice
> in a row, would require pressing up arrow ten times both the first and
> the second time. With old behavioud it would have been 5 times the
> first time and once the second time. With more than 10 commands in
> cache, the history becomes useless as it's easier to re-enter the
> command name again rather then scroll up thorugh the history even if the
> command's being run over and over again.
>
> It appears that commands which have been run previously and run again
> are not being saved in history file [0] after subsequent executions.
> To bring back previous behaviour the command should be pushed down in
> the file, e.g. similarly to zsh's "histignorealldups" option.
>
> I would appreciate any help with trying to resolve this issue.
Fixed upstream:
commit 7013b9bb70d95c660698848be1c3c1179ae68a1e
Author: Corey Thompson <cmt...@gmail.com>
Date: Sat Dec 3 20:03:40 2011 -0500
Bump duplicated commands to the most recent in command prompt history
Signed-off-by: Uli Schlachter <psyc...@znc.in>
--
Julien
pgpy2JAsvr942.pgp
Description: PGP signature
