but I can hit the up-arrow to get previous lines.
Hm. I wonder why that works for you and not for me.
Could it be that you use a *nix shell clone (rather than cmd.exe), under windows that maps the arrow keys for you?
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
I wonder why that works for you and not for me.
It works for me, too - and I'm using the cmd.exe shell.
There was a recent report of a similar situation with the perldl shell, too. A guy using windows found that the arrow keys wouldn't work for him in the perldl shell. Like you, my first thought was that he wasn't running the cmd.exe shell .... but he was. (That's as far as we got.)
I haven't a clue what could be causing the difference in behaviour. For me, it's the same behaviour on 2000, XP and Vista (SP1). The arrow keys work as expected.
Cheers, Rob
| [reply] |
Very strange! I even created a new user account and tried it there--just in case I've applied some configuration to my cmd sessions that could be influencing the problem--but it makes no difference.
None of the navigation keys--left/right/up/down/home/end--appear to doing anything at all.
No matter. I now know how to disable it, and that's preferable for me. I like my control keys to serve their designated functions anyway.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
I think it is doskey that enables up/down history list, right arrow completion, tab filename expansion... and it appears in windows xp and later, its on by default
| [reply] |
| [reply] |