From: Clem Cole <clemc@ccc.com>
To: Random832 <random832@fastmail.com>
Cc: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] V6 Console IO
Date: Fri, 24 Jul 2020 13:15:58 -0400 [thread overview]
Message-ID: <CAC20D2OVG8jDsis0OCu7LyKxMiDqDu=PhU1PCU1FwO-VDikQLw@mail.gmail.com> (raw)
In-Reply-To: <3b4e50f0-5ab9-4726-99a3-b39568b2a7bb@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On Fri, Jul 24, 2020 at 12:39 PM Random832 <random832@fastmail.com> wrote:
> On Fri, Jul 24, 2020, at 00:54, Paul Riley wrote:
> > Noel,
> >
> > Thanks for your reply.
> >
> > I had suspected that the Unix behaviour was responsible, and you've
> > made that clear with the "line at a time" assertion. I tried removing
> > echo in STTY, but haven't tried raw.
>
> You'll have a hard time exiting your program if you use raw mode - cbreak
> should be enough, and in that case ctrl-c will still work [but even in
> cbreak mode I believe there is no way to send "EOF".]
>
There is no such thing as cbreak in sixth edition.
http://man.cat-v.org/unix-6th/1/stty
It's raw or cooked. Life is more interesting ;-)
Good luck
[-- Attachment #2: Type: text/html, Size: 1652 bytes --]
next prev parent reply other threads:[~2020-07-24 17:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 2:28 Noel Chiappa
2020-07-24 4:54 ` Paul Riley
2020-07-24 16:37 ` Random832
2020-07-24 17:15 ` Clem Cole [this message]
2020-07-25 2:45 ` Random832
2020-07-24 14:34 ` Clem Cole
2020-07-25 2:48 ` Paul Riley
2020-07-25 4:02 ` John Cowan
2020-07-25 15:09 ` Clem Cole
2020-07-25 15:31 ` Richard Salz
2020-07-26 1:08 ` Random832
2020-07-27 9:11 ` Paul Riley
-- strict thread matches above, loose matches on Subject: below --
2020-07-25 17:45 Noel Chiappa
2020-07-24 14:33 Noel Chiappa
2020-07-24 14:36 ` Clem Cole
2020-07-25 1:53 ` Dave Horsfall
2020-07-24 0:18 Paul Riley
2020-07-24 2:57 ` Larry McVoy
2020-07-24 4:41 ` Paul Riley
2020-07-24 4:54 ` Paul Riley
2020-07-24 14:01 ` Larry McVoy
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='CAC20D2OVG8jDsis0OCu7LyKxMiDqDu=PhU1PCU1FwO-VDikQLw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=random832@fastmail.com \
--cc=tuhs@minnie.tuhs.org \
/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).