From: "boyd, rounin" <boyd@insultant.net>
To: "Russ Cox" <russcox@gmail.com>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Common code - isatty
Date: Thu, 14 Apr 2005 02:14:12 +0200 [thread overview]
Message-ID: <043c01c54086$e3afc5f0$9efb7d50@kilgore> (raw)
In-Reply-To: <ee9e417a050413170042e33edf@mail.gmail.com>
> fd2path is the right answer.
sure looks nice, 'cept for the strings.
> would you add a system call instead?
nope, call me old fashioned -- stat(2).
--
MGRS 31U DQ 52572 12604
next prev parent reply other threads:[~2005-04-14 0:14 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 [this message]
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
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='043c01c54086$e3afc5f0$9efb7d50@kilgore' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.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 NNTP newsgroup(s).