The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: segaloco <tuhs@tuhs.org>
Subject: [TUHS] Re: Cooked Mode (v8 shell)
Date: Mon, 23 Jan 2023 10:53:46 -0500	[thread overview]
Message-ID: <a31c330c-5761-954d-d9ed-9a49b9c1f7b6@case.edu> (raw)
In-Reply-To: <Y86tDf+ztYdGxUe3@mit.edu>

On 1/23/23 10:51 AM, Theodore Ts'o wrote:
> On Mon, Jan 23, 2023 at 09:49:08AM -0500, Chet Ramey wrote:
>> On 1/23/23 9:45 AM, Brian M Zick wrote:
>>>> 6) It ran in cooked mode.
>>>
>>> Sorry if this is obvious to everyone else: What does this phrase mean?
>>
>> It did not perform line editing, so it did not change the terminal modes
>> and read one character at a time. If you only ever read a line at a time
>> from the terminal, you can let the terminal driver do that for you.
> 
> I've never been convinced by that particular argument, since if you
> want command-line completion, the terminal driver is way too
> low-level.

But that's the point: they don't.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/


  reply	other threads:[~2023-01-23 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  7:38 [TUHS] v8 shell Rob Pike
2023-01-22 14:52 ` [TUHS] " arnold
2023-01-23 14:45   ` [TUHS] Re: Cooked Mode (v8 shell) Brian M Zick
2023-01-23 14:49     ` Chet Ramey
2023-01-23 15:51       ` Theodore Ts'o
2023-01-23 15:53         ` Chet Ramey [this message]
2023-01-23 20:40           ` Marc Donner

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=a31c330c-5761-954d-d9ed-9a49b9c1f7b6@case.edu \
    --to=chet.ramey@case.edu \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.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).