DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=fP2A1chrenZzWcq0fbHcGSjT5b7Ly
	esF5bdQq1aDc36SKhU0YreoxDyngqmwoQZvWa72tlwCHdhmWgXWWgxPw51wfGI0Q
	qJmh2AXr0HnljYVj4h+6U3iTvftCpJY8UOySh3MbKndfdg3dkgf6zOioeC0+DnDW
	bNSS4O3MmTztRA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Rich Eizenhoefer <riche@microsoft.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: From Microsoft: Windows 10 Console and Cygwin
Date: Mon, 8 Jun 2015 17:23:00 +0000
Message-ID: <BN3PR03MB1430C0664FE9E4DBBCC4FD29B4BF0@BN3PR03MB1430.namprd03.prod.outlook.com>
References: <BN3PR03MB1430B88AED4339821C7D95BEB4D50@BN3PR03MB1430.namprd03.prod.outlook.com> <20150502133833.GB12723@calimero.vinschen.de> <BN3PR03MB1430C0816A9D41BB051687A4B4D20@BN3PR03MB1430.namprd03.prod.outlook.com> <1433098286892-118602.post@n5.nabble.com> <20150601082456.GG4308@calimero.vinschen.de> <BN3PR03MB14303BAD46376DED807CFA2CB4B60@BN3PR03MB1430.namprd03.prod.outlook.com> <CAJ1KOAiG-VV2heqYSNSjwCb=s_pjxoxKaGY3SnDiy4E20yvOWw@mail.gmail.com> <BN3PR03MB1430F49F8839B66558779F3AB4B50@BN3PR03MB1430.namprd03.prod.outlook.com> <556E01FC.6060004@redhat.com> <CAB2911B-10C9-409F-B0A4-A88C3C9EB0BD@etr-usa.com> <20150608114924.GA3005@calimero.vinschen.de>
In-Reply-To: <20150608114924.GA3005@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jun 2015 17:23:00.4906 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB1432
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id t58HNGIh022149

We're hearing more and more need for something like this, not just a hidden console window but a proper bifurcation between a console server and client so to speak. I'll add the POSIX pty idea to our backlog for when we start reviewing the overall requests in this area.

--Rich

-----Original Message-----
From: Corinna Vinschen [mailto:corinna-cygwin@cygwin.com] 
Sent: Monday, June 8, 2015 4:49 AM
To: cygwin@cygwin.com
Cc: Rich Eizenhoefer
Subject: Re: From Microsoft: Windows 10 Console and Cygwin

On Jun  2 14:49, Warren Young wrote:
> On Jun 2, 2015, at 1:20 PM, Eric Blake <eblake@redhat.com> wrote:
> > 
> > On 06/02/2015 10:37 AM, Rich Eizenhoefer wrote:
> >> Can you provide more detail on changing isatty function to support Cygwin PTY's? I need to be able to support the request in our backlog.
> > 
> > As long as we are wishing, it would be awesome if Windows natively 
> > supported ptys as actual objects, instead of making cygwin have to 
> > emulate them on top of other objects.
> 
> In my ignorance of how ptys map to Windows console objects, I held off from asking for this when Mr. Eizenhoefer solicited ideas, but this is what I thought of at that time, too.
> 
> In other words, this notion of “virtual terminals” is already implemented multiple times, following a standard that specifies the expected semantics — POSIX — so why not just do that?
> 
> Why, in the end, can Windows *not* have ptys?

That's a good question. 

Basically Windows console handles are kind of one half of the equation.
They don't follow the expected semantics but they are what native Windows tools know and expect.

Opening up the other half of the equation, the server side, without forcing to start conhost, might be enough to allow emulating POSIX ptys.

But I agree, real ptys with POSIX semantics would be cool.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat