https://blogs.windows.com/buildingapps/2014/10/07/console-improvements-in-the-windows-10-technical-preview/ tl;dr: 0. The console window is now resizable. Like, by dragging on the window edges. You know, like in Windows 2.0. Wow! :) 1. Text selection and pasting now works line-by-line, not as a block of unrelated lines. ...Just like every *ix terminal program since forever. 2. Extensive keyboard text editing. It's not up to the standards of xterm plus Bash’s emacs mode, but it’s far better than they had before. 3. Keyboard copy/paste, in Windows-native flavor (Ctrl-C/V/X) and xterm flavor (Ctrl/Shift-Ins). Unfortunately, no xterm-like mouse copy/paste. I’m not giving up mintty and Bash, but it’s nice to know the occasional dip into cmd.exe won’t be such a sharp shock.
[-- Attachment #1: Type: text/plain, Size: 923 bytes --] On 08/06/2015 02:09 PM, Warren Young wrote: > https://blogs.windows.com/buildingapps/2014/10/07/console-improvements-in-the-windows-10-technical-preview/ > > tl;dr: > > 0. The console window is now resizable. Like, by dragging on the window edges. You know, like in Windows 2.0. Wow! :) > > 1. Text selection and pasting now works line-by-line, not as a block of unrelated lines. ...Just like every *ix terminal program since forever. > > 2. Extensive keyboard text editing. It's not up to the standards of xterm plus Bash’s emacs mode, but it’s far better than they had before. > > 3. Keyboard copy/paste, in Windows-native flavor (Ctrl-C/V/X) and xterm flavor (Ctrl/Shift-Ins). Unfortunately, no xterm-like mouse copy/paste. > > I’m not giving up mintty and Bash, but it’s nice to know the occasional dip into cmd.exe won’t be such a sharp shock. > Still no pseudoconsole API? [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --]
On Aug 6, 2015, at 3:10 PM, Daniel Colascione <dancol@dancol.org> wrote:
>
> Still no pseudoconsole API?
We already knew that wasn’t coming in 10. It’s on their wishlist.
On Aug 6, 2015, at 3:09 PM, Warren Young <wyml@etr-usa.com> wrote:
>
> 3. Keyboard copy/paste, in Windows-native flavor (Ctrl-C/V/X) and xterm flavor (Ctrl/Shift-Ins). Unfortunately, no xterm-like mouse copy/paste.
Oooh, I just discovered a new trap due to this feature: Ctrl-A is interpreted as “select all”, so you can’t use it for “go to beginning of line” in Bash with Emacs editing. Grrr…
[-- Attachment #1: Type: text/plain, Size: 768 bytes --] On Aug 28 14:41, Warren Young wrote: > On Aug 6, 2015, at 3:09 PM, Warren Young <wyml@etr-usa.com> wrote: > > > > 3. Keyboard copy/paste, in Windows-native flavor (Ctrl-C/V/X) and xterm flavor (Ctrl/Shift-Ins). Unfortunately, no xterm-like mouse copy/paste. > > Oooh, I just discovered a new trap due to this feature: Ctrl-A is > interpreted as “select all”, so you can’t use it for “go to beginning > of line” in Bash with Emacs editing. Grrr… Keep Rich Eizenhoefer (address on the list) in the line. He's a nice guy and really interested in everything Console. He might consider some settings which prefer application shortcuts over global shortcuts or anything which helps in such a situation, if you explain it nicely. Corinna [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
On Aug 29, 2015, at 1:24 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>
> settings which prefer application shortcuts over global shortcuts
I was thinking of it more as yet another reason to prefer mintty, and a thing to keep in mind when you must use cmd.exe for some reason, as with my recent testing of the full-screened console window on the main list.
MS is coming at it from the WordPad perspective, whereas mintty is coming at it from the xterm/tty perspective. They’re going to conflict over things like the meaning of Ctrl-A.
The only reason they haven’t broken Ctrl-C, too, is that they can do that only when there is something selected.
But the Bash/Vim use for Ctrl-V is probably also broken under Windows 10 now, so there goes the normal way of inserting literal control characters into documents, something I end up needing to do once every several months. (e.g. ^V^O to reset a terminal due to accidentally cat-ing a binary file, or hacking around with ^M to test CR/LF handling in some parser.)
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --] On Aug 29 20:09, Warren Young wrote: > On Aug 29, 2015, at 1:24 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote: > > > > settings which prefer application shortcuts over global shortcuts > > I was thinking of it more as yet another reason to prefer mintty, and > a thing to keep in mind when you must use cmd.exe for some reason, as > with my recent testing of the full-screened console window on the main > list. > > MS is coming at it from the WordPad perspective, whereas mintty is > coming at it from the xterm/tty perspective. They’re going to > conflict over things like the meaning of Ctrl-A. > > The only reason they haven’t broken Ctrl-C, too, is that they can do > that only when there is something selected. > > But the Bash/Vim use for Ctrl-V is probably also broken under Windows > 10 now, so there goes the normal way of inserting literal control > characters into documents, something I end up needing to do once every > several months. (e.g. ^V^O to reset a terminal due to accidentally > cat-ing a binary file, or hacking around with ^M to test CR/LF > handling in some parser.) That doesn't invalidate what I wrote, rather to the contrary. I'm certain that Rich would appreciate an honest bug report over grumbling behind the scenes :) Corinna [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]