The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* Re: [TUHS] screen editors / machine load
@ 2020-01-10 15:35 Noel Chiappa
  0 siblings, 0 replies; 8+ messages in thread
From: Noel Chiappa @ 2020-01-10 15:35 UTC (permalink / raw)
  To: tuhs; +Cc: jnc

    > When Bernie Greenberg did EMACS for Multics, he had a similar issue. I
    > recall reading a document with an extensive discussion of how they dealt
    > with this ... If anyone's really interested in this, and can't find it
    > themselves, I can try looking for it.

I got a request for this; a Web search turned up:

  https://www.multicians.org/mepap.html

which covers the points I mentioned (and more besides, such as why LISP was
chosen). I don't think this is the thing I remembered (which was, IIRC, an
informal note), but it does seem to be a later version of that.

	 Noel

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [TUHS] screen editors / machine load
@ 2020-01-10 14:35 Noel Chiappa
  0 siblings, 0 replies; 8+ messages in thread
From: Noel Chiappa @ 2020-01-10 14:35 UTC (permalink / raw)
  To: tuhs; +Cc: jnc

    > From: Otto Moerbeek <otto@drijf.net>

    > I believe it was not only vi itself that was causing the load, it was
    > also running many terminals in raw mode that killed performance.

I'm not familiar with the tty driver in late versions of Unix like 4.1 (sic),
but I'm very familiar with the one in V6, and it's not the raw mode _itself_
that caused the load (the code paths in the kernel for cooked and raw aren't
that different), but rather the need to wake up and run a process on every
character that was the real load.

When Bernie Greenberg did EMACS for Multics, he had a similar issue. I recall
reading a document with an extensive discussion of how they dealt with this,
especially when using the system over the ARPANET. IIRC, normal printing
characters were echoed without waking up the process; remotely, when using
the network. If anyone's really interested in this, and can't find it themselves,
I can try looking for it.

	Noel


^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [TUHS] screen editors
@ 2020-01-08  7:39 Thomas Paulsen
  2020-01-08 21:49 ` Dave Horsfall
  0 siblings, 1 reply; 8+ messages in thread
From: Thomas Paulsen @ 2020-01-08  7:39 UTC (permalink / raw)
  To: arnold; +Cc: tuhs

>What's funny is that in doing the work to get 'se' running on Georgia
>Tech's Vax, I had to learn vi.  By the time I was done, vi had become
>my main editor and had burned itself into my finger's ROMs.
I do ed/se occasionally for simple tasks, vim frequently , because it loads fast, and emacs for all bigger projects, beside liteide for golang. 



^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2020-01-11  0:31 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-10 15:35 [TUHS] screen editors / machine load Noel Chiappa
  -- strict thread matches above, loose matches on Subject: below --
2020-01-10 14:35 Noel Chiappa
2020-01-08  7:39 [TUHS] screen editors Thomas Paulsen
2020-01-08 21:49 ` Dave Horsfall
2020-01-10  8:13   ` markus schnalke
2020-01-10 13:41     ` [TUHS] screen editors / machine load Mike Markowski
2020-01-10 13:56       ` Otto Moerbeek
2020-01-10 15:00       ` Mary Ann Horton
2020-01-10 15:48         ` Clem Cole
2020-01-10 22:18           ` Adam Thornton
2020-01-11  0:30             ` Christopher Browne

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).