From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: BLODA extension: console interoperability
Date: Thu, 25 Jul 2013 23:07:00 -0000 [thread overview]
Message-ID: <51F1A863.8060403@etr-usa.com> (raw)
I don't see any console programs on the BLODA. Shouldn't it include
programs that break under Cygwin due to things like the change from
Windows console to mintty, or the pty (?) work that improves Linux/POSIX
semantics?
Then there are the even older class of programs that didn't work right
even in the cygwin.bat days. I seem to recall that programs in this
class failed because they knew too much about how the Windows console
worked, and Cygwin couldn't intercept certain direct console accesses
for some reason.
I ask only because I don't run into this sort of thing very often, so I
didn't have any examples at hand when the issue came up in a question
raised in another forum. Ideally, I'd have been able to reference a
program that comes with Windows.
The only program I currently use that I know has such problems is rather
obscure, so it wasn't a suitable example. I don't even know that it's
popular enough to be listed in this proposed BLODA extension. (It's
fsharpi.exe from the F# command line toolchain. http://goo.gl/1GOK86
I'm not even entirely sure what the problem was, since I switched to a
Windows console for it over a month ago. Something about it being
un-Ctrl-C-able when it is in certain states.)
--
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 reply other threads:[~2013-07-25 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 23:07 Warren Young [this message]
2013-07-26 2:50 ` Larry Hall (Cygwin)
2013-07-26 4:44 ` Warren Young
2013-07-26 5:02 ` Larry Hall (Cygwin)
2013-07-26 5:20 ` Andy Koppe
2013-07-26 6:13 ` Warren Young
2013-07-26 6:44 ` Christopher Faylor
2013-07-26 14:59 ` Pavel Fedin
2013-07-26 16:22 ` Christopher Faylor
2013-07-27 3:18 ` Charles Wilson
2013-07-29 9:06 ` Pavel Fedin
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=51F1A863.8060403@etr-usa.com \
--to=warren@etr-usa.com \
--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).