public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 13:38:00 -0000	[thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A209E8030CB9@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <20110509161028.GJ27739@calimero.vinschen.de>

Corinna Vinschen sent the following at Monday, May 09, 2011 12:10 PM
>Chris and I are wondering how many people are using the Windows console
>as local console window in CYGWIN=tty mode and why.

I've been using it for so long that I do not remember why - probably
because I thought it was recommended.

I did some testing yesterday and found that with CYGWIN=tty each
console gets a unique number, as visible in /bin/tty, ps, and
$(cat /proc/$$/ctty).  Without it, one gets "con" (tty and ps) or a
long, nonunique number (/proc).  I use the tty number to keep track
of console windows.

The above testing was in console where the shortcut launches bash
directly, without use of a batch file.

In the past, I've played with minty and haven't felt the need to
switch.  I did an abbreviated test (just ps) with minty and it had
tty numbers without CYGWIN=tty.  So although I'd like the Windows/DOS
console retain the ability to be tracked, I could switch to minty if
I had to.

Best wishes,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

  parent reply	other threads:[~2011-05-10 13:38 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] [this message]
2011-05-10 17:19   ` Christopher Faylor
2011-05-10 17:50     ` Christopher Faylor
2011-05-10 22:12     ` Buchbinder, Barry (NIH/NIAID) [E]
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=0105D5C1E0353146B1B222348B0411A209E8030CB9@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).