Windows 10 (Threshold) Changes To The Windows Command Prompt

Jeff here from the Windows SDK team.

This blog isn’t network related, but something else that is close to my heart, the Windows Command Prompt. I have been using and supporting
Windows NT since version 3.51, and I don’t think the command prompt has changed in all that time. But Windows 10, build 9841, brings lots of long overdue
additions.

The first things I did to every install of Windows for the last 20 years was to enable QuickEdit mode, and increase the screen buffer
size. Now QuickEdit mode is enabled, and the buffer sizes are a much more reasonable 120 x 9001. That by itself is enough of a reason for the happy
dance, but wait, there’s more!

Windows 10 now has an experimental tab. The link below doesn’t have much information at the moment.

 

 

Enable line wrapping selection – Lets you select text on multiple lines, just like Word or
notepad.

Filter clipboard contents on paste – How many times have you sent a command line to a customer and when they paste it into a command prompt it just doesn’t work correctly?
Usually this is because Outlook changes quotes and dashes.

“Now is the time for all good men to come to the aid of their country.”

Wrap text output on resize – Changes the text wrapping as soon as you resize a window. No more
re-running a command after you resize the window to see the new changes.

Enable new Ctrl key shortcuts – Ctrl+C and Ctrl+V now copy and paste just like every other app.
(Although I am partial to Ctrl+Insert and Shift+Insert, because I am left-handed.) Ctrl+A, Ctrl+F, and others also work as expected.

Extended Edit Keys
– Not much information is available on this yet.

Trim Leading zeros on selection – (Disabled by default) When selecting numbers with leading
zeros, the zero’s aren’t selected.

Numbers with a leading radix as still selected in their entirety.

Opacity – Lets you see through beneath it.

This information is based on an unreleased version of
Windows. Your mileage may vary.

/Jeff

Follow us on Twitter, www.twitter.com/WindowsSDK.