Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by hota_mazi on Friday November 18, 2016 @03:47PM (#12989948)

What drove me away from Terminal.app was the fact that I can't use command-1/2/3 to switch tabs. Ctrl-tab doesn't work either.

Did I miss something?

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by thebspatrol on Friday November 18, 2016 @03:57PM (#12990012)

CMD + { and CMD + }

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by hota_mazi on Friday November 18, 2016 @04:48PM (#12990356)

Thanks but... yuck. Any way I can remap these?

Cmd-<number> is a pretty standard way to jump to tabs (and arguably, Ctrl-tab as well).

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by eridius on Friday November 18, 2016 @07:40PM (#12991216)

⌃⇥ actually does work in Terminal.app. And in fact, ⌃⇥ and ⌃⇧⇥ are the official keyboard shortcuts in the menu, with ⌘{ and ⌘} being undocumented aliases. This is also how Safari works too.

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by skissane on Friday November 18, 2016 @04:06PM (#12990077)

I wonder why they chose ⌘{ and ⌘} instead of ⌘[ and ⌘]. With the later you don't need to hold down SHIFT (at least on US keyboard layout.)

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by eridius on Friday November 18, 2016 @07:40PM (#12991224)

Because it's the same keyboard shortcuts that Safari uses, and in Safari ⌘[ and ⌘] navigate the history stack.

[ Parent | on HN ]