This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: Windows 10 console slightly less horrid than before
- From: Warren Young <wyml at etr-usa dot com>
- To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
- Date: Sat, 29 Aug 2015 20:09:21 -0600
- Subject: Re: Windows 10 console slightly less horrid than before
- Authentication-results: sourceware.org; auth=none
- References: <F5F37B46-4096-494B-AF31-B15AE2E596DB at etr-usa dot com> <75B1FA36-302C-4168-82F2-FA68029679D1 at etr-usa dot com> <20150829072404 dot GC29802 at calimero dot vinschen dot de>
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
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.)