Seems to me that these are 'sort of' the same thing. It may be a good idea to give the appearance of 527, by doing 484. What I mean is that if you look at the 'actual' history, you probably want to know what order you typed commands, even with duplicates, but you don't necessarilly want to use up arrow to back through every single duplicate command in an attempt to find one you typed five minutes earlier, even if you do give it part of the command to start with, as in 484, it can still run through duplicates you don't need or want. I think a basic filter that skips duplicates in the history as you scroll through it would solve the problem in general for actually using it, while keeping the total history, including duplicates, intact when requested in script or through the menu option. Maybe an option to retrieve a filtered list could be added to script as well, just for those that want to avoid duplication there too, though I don't see the point in that case myself. I suspect both requests touch on the same issue and it is the use of the keypad to scroll through and find a command that is the real issue for both cases.
Suggestions 484 and 527
Posted by Shadowfyr on Tue 05 Oct 2004 04:46 PM — 2 posts, 7,644 views.
Er, yes. I usually hit Ctrl+H and pick it from the list if I have to go back more than a couple.