From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.12
Date: Sat, 31 Mar 2012 12:02:00 -0000 [thread overview]
Message-ID: <4F76F230.5050302@towo.net> (raw)
In-Reply-To: <announce.20120330113350.GA12620@calimero.vinschen.de>
Am 30.03.2012 13:33, schrieb Corinna Vinschen:
> ...
> - Fix a bug in controlling tty handling when duplicating a console descriptor.
Hi, when I read this, I wondered whether this bug could be fixed:
http://sourceware.org/bugzilla/show_bug.cgi?id=513
but it isn't.
I had later found (and reported to cygwin-developers) that the terminal
response to terminal queries (like cursor position request or device
attribute request) is placed in the wrong buffer because there are
different objects (descriptors?) for stdin and stdout, so the response
would stay in Nirvana and never reach the application. (And it used to
work in CYGWIN=tty mode because curiously, in that case, the console
handles would have been shared for stdin and stdout.)
Since you seem to have just looked at this area of the console code,
could you give it check?
Kind regards,
Thomas
--
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:[~2012-03-31 12:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 12:48 Corinna Vinschen
2012-03-30 12:53 ` Eric Blake
2012-03-30 16:54 ` Nellis, Kenneth
2012-03-31 8:03 ` Denis Excoffier
2012-03-31 12:02 ` Thomas Wolff [this message]
2012-04-02 8:07 ` Corinna Vinschen
2012-04-02 17:06 ` Christopher Faylor
2012-04-02 18:51 ` Thomas Wolff
2012-04-02 18:54 ` Christopher Faylor
2012-04-01 20:06 Ken
2012-04-01 20:29 ` Christopher Faylor
2012-04-01 22:46 ` Christopher Faylor
2012-04-01 23:51 ` Ken
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=4F76F230.5050302@towo.net \
--to=towo@towo.net \
--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).