XP cmd.com adjust command-history setting

[R.Wieser]

Hello All,

I use the CMD.EXE "dos-box" quite often, and have troubles with its
command-history.

Due to what I'm doing (writing something, testing it -- rinse-and-repeat) I
quite often use the up-arrow to reach a previously-typed command-line and
than press the enter-key to execute it.

The problem is that when I do the above a number of times I unexpectedly get
a fully different line than the one I executed previously or the time before
that.

Someone explained to me the logic behind that behaviour, and it was indeed
quite logical (just like software random-generators are logical but
not-to-be-followed by a mere mortal) -- but not a behaviour I want.

So, my question: can I change the behaviour of the commandline-history in
such a way that it *allways* starts at the end of the list (just like
"doskey" did in 'the good-old days') ?

If not, is there a way to replace that commandline-hisory module with
another one ?

Regards,
Rudy Wieser

 

[Zaphod Beeblebrox]

Hello All,

I use the CMD.EXE "dos-box" quite often, and have troubles with
its command-history.

So, my question: can I change the behaviour of the
commandline-history in such a way that it *allways* starts at the
end of the list (just like "doskey" did in 'the good-old days') ?

Not that I know of. If you find a way, be sure to post back as I find
it annoying on occasion as well.

If not, is there a way to replace that commandline-hisory module
with another one ?

I searched Google with "cmd command history replacement" and got a
couple of promising looking hits - you may need to replace cmd.exe
altogether, though.

Something that might help is to use F7 to bring up the list of recent
commands and pick the command from the list .

 

[R.Wieser]

Hello Zaphod,

Thanks for the reply. I hoped that it would be a matter changing a(n
unknown) setting, but alas ...

Using F7 is one possibility, pressing "PageDown" before cursor-up seems to
be another.

By the way: Its possible to disable the in-build command-history altogether,
but I've not seen any mentioning of a possibility to load a seperate
command-history ontop of the disabled one (DosKey refuses to work).

Regards,
Rudy Wieser


-- Origional message: