Command Prompt Properties

  • Thread starter Thread starter John C. Frickson
  • Start date Start date
J

John C. Frickson

The other day, I started a command-line program. Turns out it was going
to take quite a while to finish. So I did my usual "alt+space, p" to
bring up properties, ctrl+tab to the Fonts tab, pick a small font,
ctrl+tab to the Layout tab, and set the window size to 2 rows high, and
30 columns wide, hit enter, move the window to a corner of the screen
so I can monitor progress.

Then I bring up another command prompt, and am I surprised that it's
got a small font and is 30x2!

What happened to the prompt to "Apply properties to current window only"
or "Modify shortcut that started this window"? It seems like Vista now
assumes you always want to make any changes the default.

Is there any way to get the old pre-Vista behavior back?
 
John C. Frickson said:
Is there any way to get the old pre-Vista behavior back?
Click to expand...

Hi John,

I've repro'ed this behaviour and can confirm that Vista does appear to skip
the "Current Window only?" dialogue. So, you're not going crazy (I mention
this because my first reaction was "he's going crazy"! But then I tried it.)

It does seem like an unfortunate regression.

I've tried to compare the behaviour of CMD on XP and Vista in the debugger,
to see what the difference might be. No solution as of yet; but I strongly
suspect there's no easy fix - I'm not seeing any kind of
"RestoreXPbehaviour" registry key in the debugged code.

Maybe on of the Microsoft guys can comment. Otherwise, I'll keep debugging
and post any findings here.
 
Hi John,

I've repro'ed this behaviour and can confirm that Vista does appear to skip
the "Current Window only?" dialogue. So, you're not going crazy (I mention
this because my first reaction was "he's going crazy"! But then I tried it.)

It does seem like an unfortunate regression.

I've tried to compare the behaviour of CMD on XP and Vista in the debugger,
to see what the difference might be. No solution as of yet; but I strongly
suspect there's no easy fix - I'm not seeing any kind of
"RestoreXPbehaviour" registry key in the debugged code.

Maybe on of the Microsoft guys can comment. Otherwise, I'll keep debugging
and post any findings here.
Click to expand...

Thanks, I appreciate it!
 
Back
Top