From: Daniel Colascione <dancol@dancol.org>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: Windows 10 console slightly less horrid than before
Date: Thu, 06 Aug 2015 21:10:00 -0000 [thread overview]
Message-ID: <55C3CD30.1080307@dancol.org> (raw)
In-Reply-To: <F5F37B46-4096-494B-AF31-B15AE2E596DB@etr-usa.com>
[-- 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 --]
next prev parent reply other threads:[~2015-08-06 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 21:09 Warren Young
2015-08-06 21:10 ` Daniel Colascione [this message]
2015-08-06 21:11 ` Warren Young
2015-08-28 20:41 ` Warren Young
2015-08-29 7:24 ` Corinna Vinschen
2015-08-30 2:09 ` Warren Young
2015-08-30 10:28 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C3CD30.1080307@dancol.org \
--to=dancol@dancol.org \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).