From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Common code - isatty
Date: Thu, 14 Apr 2005 10:01:36 +1000 [thread overview]
Message-ID: <775b8d19050413170155776984@mail.gmail.com> (raw)
In-Reply-To: <200504132352.j3DNqJJ19726@augusta.math.psu.edu>
Dan! Stop being so blunt and correct!
20 years ago it became clear that there was no bloody way
to determine if a program was being run interactively.
Given that ... the various hacks are convenient.
e.g. "rc" rather than "rc -i" but still ... It is a cesspool.
brucee
On 4/14/05, Dan Cross <cross@math.psu.edu> wrote:
> "Ronald G. Minnich" <rminnich@lanl.gov> writes:
> > On Wed, 13 Apr 2005, Russ Cox wrote:
> > > i'm hesitant to put it in a library because most programs (e.g., ls)
> > > should not behave differently when running on a console. if it's there,
> > > it may be overused like in unix.
> >
> > good call. don't do it. We're fighting a lot of isatty() stupidity on our
> > clusters, and it's a nightmare. I agree that it would get overused ...
>
> Or put it into libidiot.h just so there's only one copy of it.
>
> Oh, you think I'm joking?
>
> - Dan C.
>
>
next prev parent reply other threads:[~2005-04-14 0:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 13:20 Einar Karttunen
2005-04-13 21:50 ` Russ Cox
2005-04-13 23:26 ` Ronald G. Minnich
2005-04-13 23:52 ` Dan Cross
2005-04-13 23:57 ` boyd, rounin
2005-04-14 0:00 ` Russ Cox
2005-04-14 0:14 ` boyd, rounin
2005-04-14 0:18 ` Russ Cox
2005-04-14 0:22 ` Bruce Ellis
2005-04-14 0:38 ` Dan Cross
2005-04-14 1:02 ` boyd, rounin
2005-04-14 0:56 ` jmk
2005-04-14 0:01 ` Bruce Ellis [this message]
2005-04-14 0:39 ` Dan Cross
2005-04-14 17:14 ` Ronald G. Minnich
2005-04-14 17:29 ` Rob Pike
2005-04-14 19:25 ` Ronald G. Minnich
2005-04-14 23:23 ` Bruce Ellis
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=775b8d19050413170155776984@mail.gmail.com \
--to=bruce.ellis@gmail.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).