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

On Tue, 26 Jan 2021 12:52:25 +0900
Takashi Yano 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.
>  --> Respecting Corinna's opinion, we decided not to implement this.
> v3: Fix typeahead input issue in GDB. Several other bugs have also
>     been fixed.
> v4: Change the conditions for calling transfer_input() slightly in
>     reset_switch_to_pcon() to avoid calling it if uncecessary or
>     with no effect.
> v5: Small bug fix in v4.

I have another fix for v5. Please wait for v6.

Takashi Yano <>

      parent reply	other threads:[~2021-01-26  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  3:52 Takashi Yano
2021-01-26  3:52 ` [PATCH v5 1/4] Cygwin: pty: Inherit typeahead data between two input pipes Takashi Yano
2021-01-26  3:52 ` [PATCH v5 2/4] Cygwin: pty: Keep code page between non-cygwin apps Takashi Yano
2021-01-26  3:52 ` [PATCH v5 3/4] Cygwin: pty: Make apps using console APIs be able to debug with gdb Takashi Yano
2021-01-26  3:52 ` [PATCH v5 4/4] Cygwin: pty: Allow multiple apps to enable pseudo console simultaneously Takashi Yano
2021-01-26  8:45 ` Takashi Yano [this message]

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