The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: TUHS <tuhs@tuhs.org>, steve jenkin <sjenkin@canb.auug.org.au>
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Wed, 2 Nov 2022 23:01:29 -0400	[thread overview]
Message-ID: <CAC20D2OEgK_hdvug9LxO4X=jLnCtRp44Ttj7hWP85p5eebO_sQ@mail.gmail.com> (raw)
In-Reply-To: <emc238c437-aa92-43b8-bb56-2eac700fab91@6b571117.com>

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

The 33 and 28 needed at least two null chars after the <CR> or it would
lose chars as there was no buffering.  The Unix driver has the CR delay
modes to support it.  It’s UART as it were was mechanical and a real work
of art.   I remember spending a few hours trying to figure out how it
worked.

As for the LA120 yeah you really needed to use real flow control which
could be a problem on DL11s and DZs ports.   SW flow was less than
prefect.  However, the Able version of the DH supported flow in hardware
(RTS/CTS style) so you could set them to interface with the host at 960cps
and then print as fast as possible swiping back and forth on the paper as
the local microprocessor in the decwritter buffered everything.

On Wed, Nov 2, 2022 at 9:48 PM Ronald Natalie <ron@ronnatalie.com> wrote:

> I’m not sure the model 33 required a carriage return delay.   At 110 baud
> it had plenty of time to move the carriage. back.
> Other printers (especially faster ones) weren’t so lucky, but the LA36
> decwriter had a catchup mode to print the backlog after a return.
> The LA120 was boustrophedonic so returns weren’t as much of an issue.
>
> ------ Original Message ------
> From "John P. Linderman" <jpl.jpl@gmail.com>
> To jason-tuhs@shalott.net
> Cc "steve jenkin" <sjenkin@canb.auug.org.au>; "TUHS" <tuhs@tuhs.org>
> Date 11/2/2022 12:20:12 PM
> Subject [TUHS] Re: Early Unix and Keyboard Skills
>
>
>
> On Wed, Nov 2, 2022 at 3:02 PM <jason-tuhs@shalott.net> wrote:
>
>>
>> > I’ve never heard anyone mention keyboard skills with the people of the
>> > CSRC - doesn’t anyone know?
>>
>>
>> https://www.tuhs.org/Archive/Documentation/AUUGN/AUUGN-V05.4.pdf (p23)
>>
>> > History tells us that the guys who designed [UNIX] did their own typing
>> > into the machine.  It seems to me that because of this, the main reason
>> > that UNIX enjoys/suffers from terse input and output is not through any
>> > intellectual design decisions made at some early stage but because the
>> > UNIX designers were just bad typists working on slow peripherals.
>>
>>
>>   -Jason
>>
>
> Mostly rampant speculation on my part, but with 110 baud modems, 10
> characters per second right?,
> and added delays for carriage returns, it was the peripherals that
> encouraged brevity. Code would be
> viewed multiple times, but entered roughly once.
>
> --
Sent from a handheld expect more typos than usual

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

  parent reply	other threads:[~2022-11-03  3:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy
2022-11-02 13:27     ` Steffen Nurpmeso
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole [this message]
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas McIlroy

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='CAC20D2OEgK_hdvug9LxO4X=jLnCtRp44Ttj7hWP85p5eebO_sQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=ron@ronnatalie.com \
    --cc=sjenkin@canb.auug.org.au \
    --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).