The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Random832 <random832@fastmail.com>
To: TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CR delay for VT05
Date: Mon, 20 Jul 2020 00:28:09 -0400	[thread overview]
Message-ID: <798e20fd-addf-4f9a-a4f9-b3dabb8ebe3c@www.fastmail.com> (raw)
In-Reply-To: <20200719233207.BB69D2D9E6DD@macaroni.inf.ed.ac.uk>

On Sun, Jul 19, 2020, at 19:32, Richard Tobin wrote:
> Looking at the 6th edition man page tty(2), I see
> 
>      Carriage-return delay type 1 lasts about .08 seconds and is
>      suitable for the Terminet 300.  Delay type 2 lasts about .16
>      seconds and is suitable for the VT05 and the TI 700.  Delay
>      type 3 is unimplemented and is 0.
> 
>      New-line delay type 1 is dependent on the current column and
>      is tuned for Teletype model 37's.  Type 2 is useful for the
>      VT05 and is about .10 seconds.  Type 3 is unimplemented and
>      is 0.
> 
> Why would the VT05 (a VDU) need a delay for carriage return?
> I can just about imagine that it might need one for linefeed
> if it shifted the characters in memory.

According to the VT05 manual, it only required a line feed delay [and other functions, most of which other than erase screen had in common that they moved or could move the cursor's vertical position] and only needed about .02 seconds ["slightly greater than one full cycle of the AC line", and the examples given were 1 character per 600 baud]

https://vt100.net/docs/vt05-rm/chapter2.html

  reply	other threads:[~2020-07-20  4:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 23:32 Richard Tobin
2020-07-20  4:28 ` Random832 [this message]
2020-07-29 23:23 ` Dave Horsfall
2020-07-30  0:56   ` Clem Cole
2020-07-30 16:42   ` Paul Winalski
2020-08-12  2:09     ` Dave Horsfall

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=798e20fd-addf-4f9a-a4f9-b3dabb8ebe3c@www.fastmail.com \
    --to=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).