From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Who's using "CYGWIN=tty" and why?
Date: Tue, 10 May 2011 22:12:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A209E8030CCE@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <20110510171846.GA27537@ednor.casa.cgf.cx>
Christopher Faylor sent the following at Tuesday, May 10, 2011 1:19 PM
>If we changed the /dev/console to /dev/consN (where N is a unique number
>for each console window) would that address your use case?
Yes, it works for me if there would be a reasonably small (preferably
single digit) number in the output of tty or ps.
>You would not be able to do something like echo foo >/dev/cons4 and have
>foo be echoed another console window though.
Since I haven't been on a real Unix/POSIX machine since the late '80s,
I'd forgotten about that. Now you made me want to DO it! :-)
>Eliminating the special case of tty handling
>would simplify the cygwin pty layer, shrink the size of the DLL, and
>generally make Cygwin a little easier to maintain.
Even if you don't accommodate me, that's OK, if your lives will be
easier. As I wrote, if I find that I really miss tty identification,
I can learn to use mintty. (Or maybe I should just switch - but not
today.)
Thank to you all for your work on cygwin.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
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:[~2011-05-10 22:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 16:11 Corinna Vinschen
2011-05-09 16:21 ` Henry S. Thompson
2011-05-09 16:34 ` Corinna Vinschen
2011-05-09 17:37 ` Henry S. Thompson
2011-05-10 8:56 ` Corinna Vinschen
2011-05-10 1:42 ` rifter rifter
2011-05-09 16:32 ` Andrew Schulman
2011-05-09 16:40 ` Edward Lam
2011-05-09 17:03 ` Ken Brown
2011-05-09 20:00 ` Christopher Faylor
2011-05-09 20:06 ` Christopher Faylor
2011-05-09 17:41 ` Lee Maschmeyer
2011-05-09 17:52 ` Samuel Thibault
2011-05-09 20:05 ` Christopher Faylor
2011-05-09 20:23 ` Samuel Thibault
2011-05-10 14:09 ` Corinna Vinschen
2011-05-10 14:59 ` Andy Koppe
2011-05-10 13:39 ` Lee Maschmeyer
2011-05-10 15:36 ` Charles Wilson
2011-05-10 16:45 ` Lee Maschmeyer
2011-05-09 21:14 ` Karl M
2011-05-09 21:39 ` Jeremy Bopp
2011-05-09 22:27 ` Thomas Wolff
2011-05-09 23:18 ` Christopher Faylor
2011-05-10 2:30 ` Claude Sylvain
2011-05-10 8:29 ` Csaba Raduly
2011-05-10 9:02 ` Corinna Vinschen
2011-05-10 13:38 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-05-10 17:19 ` Christopher Faylor
2011-05-10 17:50 ` Christopher Faylor
2011-05-10 22:12 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2011-05-10 22:17 ` Christopher Faylor
2011-05-10 14:51 ` Bernhard Ege
2011-05-10 14:58 ` Jeremy Bopp
2011-06-08 19:30 ` Christopher Faylor
2011-05-10 21:18 Len Giambrone
2011-05-11 6:35 ` Corinna Vinschen
2011-05-11 10:12 ` David Antliff
2011-05-11 15:02 ` Edward Lam
2011-05-11 15:40 ` Christopher Faylor
2011-05-11 16:00 ` Edward Lam
2011-05-11 16:00 ` Andy Koppe
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=0105D5C1E0353146B1B222348B0411A209E8030CCE@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--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).