9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] isatty
Date: Wed, 23 Jan 2002 14:43:20 +0100	[thread overview]
Message-ID: <3C4EBDF8.FCA415D6@strakt.com> (raw)
In-Reply-To: <20020123131345.E12DA199BF@mail.cse.psu.edu>

presotto@closedmind.org wrote:
> The version comparison is an overkill and potentially wrong since
> whatever is implementing /dev/cons may decide to update the
> version each write, as is our practice in other places.

I had this in mind as I wrote it and I asked the question
because I wanted an answer from the source.

> That should work in general as long as the namespace hasn't
> been changed twixt the opening of the fd and the dirstat.
> Otherwise /dev/cons may be under a different mount point
> number and hence a different c.dev.

Sure.

> The question isatty is usually trying to answer is
> "does the fd has an interacting user behind it?".  A
> hard question to answer in a world where the geography
> can shift so easily.

True.  But Python seems to really like you to be able to call
isatty.  Whether it wants to do it or whether it's part of the
'os' module is a question I don't want to know and isatty is
a function I never want to call.

The crawling across broken glass [aka dealing with configure
and configure based code] was vastly outweighed by the buzz
I got from using Plan 9.


  reply	other threads:[~2002-01-23 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 13:13 presotto
2002-01-23 13:43 ` Boyd Roberts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-23 15:26 Russ Cox
2002-01-23 11:56 Boyd Roberts
2001-02-14 15:45 rog
2001-02-14 15:09 Yehuda Tiram
     [not found] <rob@plan9.bell-labs.com>
2001-02-14 13:51 ` rob pike
2001-02-14 16:42   ` Scott Schwartz
2001-02-14 13:48 rog

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=3C4EBDF8.FCA415D6@strakt.com \
    --to=boyd@strakt.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).