From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.3
Date: Sat, 07 Sep 2019 03:32:00 -0000 [thread overview]
Message-ID: <20190907123228.0906d944716b058213969acd@nifty.ne.jp> (raw)
In-Reply-To: <42e43067-e388-709c-d75a-95c5ba055079@towo.net>
On Fri, 6 Sep 2019 12:02:36 +0200
Thomas Wolff wrote:
> A tool that sets up conpty itself (rawpty from
> https://github.com/Biswa96/wslbridge2) does not work anymore with
> conpty-enabled cygwin. This suggest that double-conpty enabling may be
> interfering.
> Unfortunately, I have not yet had the time to checkout the patch code in
> detail, but my suspicion is that conpty may be enabled always, while it
> should in fact be activated only if a non-cygwin program is run.
> Please check out on this.
I have not looked into this yet, but as you might expect, the pseudo
console is always enabled behind even if it is not used.
Owing to this, a cygwin program which directly accesses the console,
as your previous test case, can work normally by just switching the
r/w pipe to pseudo console side.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-09-07 3:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 12:47 Corinna Vinschen
2019-08-29 16:51 ` Biswapriyo Nath
2019-08-30 8:11 ` Corinna Vinschen
2019-08-30 19:16 ` Takashi Yano
2019-08-30 20:21 ` Corinna Vinschen
2019-08-31 3:58 ` Biswapriyo Nath
2019-08-31 4:21 ` Takashi Yano
2019-09-01 6:32 ` Biswapriyo Nath
2019-09-02 8:17 ` Corinna Vinschen
2019-09-03 9:28 ` Biswapriyo Nath
2019-09-03 10:48 ` Corinna Vinschen
2019-09-05 18:11 ` Jim Reisert AD1C
2019-09-06 2:23 ` Ken Brown
2019-09-06 5:22 ` Jim Reisert AD1C
2019-09-06 10:03 ` Thomas Wolff
2019-09-07 3:32 ` Takashi Yano [this message]
2019-09-07 11:53 ` Thomas Wolff
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=20190907123228.0906d944716b058213969acd@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@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).