public inbox for
 help / color / mirror / Atom feed
From: Takashi Yano <>
Subject: Re: [PATCH v2 0/4] Improve pseudo console support.
Date: Fri, 22 Jan 2021 20:40:26 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 22 Jan 2021 10:50:28 +0100
Corinna Vinschen wrote:
> On Jan 22 05:58, Takashi Yano via Cygwin-patches wrote:
> > The new implementation of pseudo console support by commit bb428520
> > provides the important advantages, while there also has been several
> > disadvantages compared to the previous implementation.
> > 
> > These patches overturn some of them.
> > 
> > The disadvantage:
> >  1) The cygwin program which calls console API directly does not work.
> > is supposed to be able to be overcome as well, however, I am not sure
> > it is worth enough. This will need a lot of hooks for console APIs.
> Definitely not.  We should really not cave in to such expectations.
> Cygwin apps are POSIX apps in the first place and should use the API
> provided by Cygwin and other Cygwin libs.  Yes, there are border cases
> like the X server or cygrunsrv, but these are limited and should stay
> limited.

I agree. I will stop working on it.

Takashi Yano <>

  reply	other threads:[~2021-01-22 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 20:58 Takashi Yano
2021-01-21 20:58 ` [PATCH v2 1/4] Cygwin: pty: Inherit typeahead data between two input pipes Takashi Yano
2021-01-21 20:58 ` [PATCH v2 2/4] Cygwin: pty: Keep code page between non-cygwin apps Takashi Yano
2021-01-21 20:58 ` [PATCH v2 3/4] Cygwin: pty: Make apps using console APIs be able to debug with gdb Takashi Yano
2021-01-21 20:58 ` [PATCH v2 4/4] Cygwin: pty: Allow multiple apps to enable pseudo console simultaneously Takashi Yano
2021-01-22  9:50 ` [PATCH v2 0/4] Improve pseudo console support Corinna Vinschen
2021-01-22 11:40   ` Takashi Yano [this message]
2021-01-22 12:20 ` Corinna Vinschen
2021-01-25  9:37   ` Takashi Yano

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).