Because that is a huge fuss to do what practically every other app can easily do by dragging the border, including other windows apps.
Sometimes you need to change your prompt to be a different size and an annoying 5 step thing is a big fuss
[deleted]
He/she is referring to dynamically adjusting the characters size (its line wrap) when resizing the window. You can even resize the command prompt to fullscreen but the lines wrap to 105 characters by default.
Because some of us have to deal with hundreds/thousands of servers. Lots of Windows boxes without Chef/Puppet bootstrapping them is a miserable experience. I don't know how many times I've disabled IEESC and made cmd quickedit enabled in my life just to be able to use the box (prior to doing it via bootstrapping).
Let me enlighten you then. Just create a shortcut to the cmd prompt, change the settings in the shortcut and keep a copy of that shortcut. The seetings for teh command prompt are saved in the shortcut. Now you just have to go around with it on your USB key and double-click on it to have a command-prompt with all your settings already done.
You can thank me later.
Re:Microsoft announces the Surface Pro 3
by hamburglar on Tuesday May 20, 2014 @06:33PM
(#7775630)
I wish all other windows were this easy to resize. I could simply have an array of shortcuts for all the different browser window sizes I might want. It's a much better system, really. Thank you later? I'm thanking you right now! Thank you.
Re:Microsoft announces the Surface Pro 3
by digitalinfinity on Tuesday May 20, 2014 @03:37PM
(#7774702)
Here's the regkey that controls this setting: http://technet.microsoft.com/en-us/library/cc978570.aspx
Should be fairly easy to script deploying that to all your machines.
Re:Microsoft announces the Surface Pro 3
by hamburglar on Tuesday May 20, 2014 @06:44PM
(#7775666)
Long, long ago, I wanted a way to launch arbitrary numbers of CMD.EXE windows with arbitrarily-chosen foreground and background colors. The standard settings only let you store a finite number of color entries (something like 16) to choose from. However, the registry key it finds the settings in is based on the executable name, so if you make a copy of cmd.exe called cmdb.exe and run it, you have N more slots of colors to choose from. So I wrote a little hack that took --fgcolor rrggbb --bgcolor rrggbb values and then made a hard link to cmd.exe in the temp directory called something like cmd_rrggbb_rrggbb.exe, set up the appropriate registry keys, and then invoked it with whatever other args you provided. Subsequent invocations with the same args would find the temp executable and reuse it. It was an absurd hack, but it worked really well and it amused me to write it. edit: and is a testament to how idiotic the CMD settings scheme is.
I never understood why some people make such a big fuss out of it.