The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Diomidis Spinellis <dds@aueb.gr>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: vi in cooked mode?
Date: Thu, 3 Nov 2022 16:27:45 -0400	[thread overview]
Message-ID: <CAC20D2PNWMh0SQ8THoVCGpNjRmWqzO6=6QH6EZCKmqJZ4KRcTg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OFhwHzb0CzQRN=+wzqjy_ygULGE56rcsqKbHGE_cZB0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

I should say -- UNIX  (Gosling) EMACS came from CMU ....
ᐧ

On Thu, Nov 3, 2022 at 4:26 PM Clem Cole <clemc@ccc.com> wrote:

>
>
> On Thu, Nov 3, 2022 at 3:44 PM Diomidis Spinellis <dds@aueb.gr> wrote:
>
>> Was I misled?  Was there perhaps a hacked version of vi that worked in this
>> way?
>>
> I think you may be mixing a few stories ... and features ...
>
>
> v6 vs v7 PDP-11 vs Vax much less vi vs emacs.
> Some thoughts ...
>
> 1.) Emacs came from CMU and only a few years later after the Vax had was
> stable (post 4.1BSD)
> 2.) emacs was not so much prohibited as it was slow, it needed megabytes
> of memory -- that was limit.
> 3.) By the time emacs comes on the scene, workstations are showing up, so
> you did not have 20 students on a vax to UCB.
> 4.) Raw mode was a V6 feature for PDP-11, by the time of the Vax the TTY
> was using V7 using CBREAK (1/2 cooked) which still allows canonicalization
>
> ᐧ
>

[-- Attachment #2: Type: text/html, Size: 3140 bytes --]

  reply	other threads:[~2022-11-03 20:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 19:43 [TUHS] " Diomidis Spinellis
2022-11-03 20:26 ` [TUHS] " Clem Cole
2022-11-03 20:27   ` Clem Cole [this message]
2022-11-03 20:55   ` Warner Losh
2022-11-03 21:34     ` Clem Cole
2022-11-03 22:28       ` Warner Losh
2022-11-03 22:52         ` Ron Natalie
2022-11-04  6:43       ` Lars Brinkhoff
2022-11-04 15:18         ` Dan Cross
2022-11-04 17:54           ` Lars Brinkhoff
2022-11-04 18:33   ` Ron Natalie
2022-11-04 23:42     ` Theodore Ts'o
2022-11-05  0:45       ` Dave Horsfall
2022-11-05  1:02         ` Larry McVoy
2022-11-05  1:25           ` Bakul Shah
2022-11-05  1:40             ` Larry McVoy
2022-11-05  2:31               ` Rich Salz
2022-11-05  3:44                 ` Bakul Shah
2022-11-05 18:34               ` Theodore Ts'o
2022-11-05  9:29           ` Otto Moerbeek via TUHS
2022-11-04 22:13 ` Mary Ann Horton
2022-11-03 20:17 Noel Chiappa

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='CAC20D2PNWMh0SQ8THoVCGpNjRmWqzO6=6QH6EZCKmqJZ4KRcTg@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=dds@aueb.gr \
    --cc=tuhs@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).