From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] isatty
Date: Wed, 14 Feb 2001 15:45:53 +0000 [thread overview]
Message-ID: <20010214144102.73D9C19A1D@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
i was wondering whether it might not be useful
for the terminal handler (win/rio) to print a prompt
of some kind when it got a read request on /dev/cons.
that way you get a prompt for all other programs too
(e.g. db(1)) without the clutter of isatty() and the like.
only problem is you wouldn't be sure quite which
program was asking for input. hmm, maybe not quite
such a good idea after all.
rog.
[-- Attachment #2: Type: message/rfc822, Size: 3117 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 184 bytes --]
Yeah. For purity and consistency, I tried to get TD to forget
about prompting in rc, just have it run commands, but he
caved in to pressure from less clean-minded people.
-rob
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1374 bytes --]
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] isatty
Date: Wed, 14 Feb 2001 13:48:40 0000
Message-ID: <20010214124400.7C58819A16@mail.cse.psu.edu>
> since the idea is that what i see from
> ls
> should be a good guide to what grep sees in
> ls | grep '\.c'
> then yes, that isatty is indeed a bad idea
mind you, plan 9 isn't entirely innocent in this
respect, c.f. /sys/src/cmd/rc/exec.c:/Isatty
next reply other threads:[~2001-02-14 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 15:45 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 15:26 Russ Cox
2002-01-23 13:13 presotto
2002-01-23 13:43 ` Boyd Roberts
2002-01-23 11:56 Boyd Roberts
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=20010214144102.73D9C19A1D@mail.cse.psu.edu \
--to=rog@vitanuova.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).