The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Tom Lyon via TUHS <tuhs@tuhs.org>
To: Adam Thornton <athornton@gmail.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Tom Lyon's 3270 driver for UTS
Date: Tue, 21 Jun 2022 07:18:33 -0700	[thread overview]
Message-ID: <CAAOGWQgk63yWf6XdB=pSH9KWkRQu3LqVmZnZrKb9tszrjYq4QQ@mail.gmail.com> (raw)
In-Reply-To: <49B9445A-748C-40A8-A28E-F531FD95F741@gmail.com>

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

Thanks, Adam.  I've always been proud of that driver.

Further credit - 'ned' was written by Dan Walsh (not the Redhat one), and,
like vi, it has 'ed' buried in it so all the familiar stuff just works.

It's possible to use UTS with ASCII terminals, but the hardware only
supports half-duplex, buffered, mode! I suspect it'd be possible to hack
the 270x emulator in Hercules to make it appear really full-duplex - then
one could add the real 'vi', etc.  But that would not be faithful emulation.

On Mon, Jun 20, 2022 at 7:56 PM Adam Thornton <athornton@gmail.com> wrote:

> While I know that there are people here who like good old ed...I've been
> playing with UTS under VM/370.  This version is from 1981 and I think it's
> v7.  But the important thing is that Tom Lyon wrote a 3270 terminal driver,
> and it comes with ned, which is a screen editor that feels a lot like
> XEDIT--which wasn't even in CMS at that point, although EE has been added
> to the VM370 Community Edition I'm using.  And the man pages are fullscreen
> as well.
>
> UTS is very, very usable because of that.  This really is a wonderful
> terminal driver.
>
> So, thank you, Tom!
>
> Adam



-- 
- Tom

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

      parent reply	other threads:[~2022-06-21 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  2:56 [TUHS] " Adam Thornton
2022-06-21  3:41 ` [TUHS] " Larry McVoy
2022-06-21 14:18 ` Tom Lyon via TUHS [this message]

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='CAAOGWQgk63yWf6XdB=pSH9KWkRQu3LqVmZnZrKb9tszrjYq4QQ@mail.gmail.com' \
    --to=tuhs@tuhs.org \
    --cc=athornton@gmail.com \
    --cc=pugs@ieee.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).