From: Humm <hummsmith42@gmail.com>
To: Phil Budne <phil@ultimate.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] vi on v7
Date: Thu, 6 Jan 2022 01:20:36 +0000 [thread overview]
Message-ID: <YdZD5HHQ3+5K/Z1w@beryllium.local> (raw)
In-Reply-To: <202201051734.205HYqeq042817@ultimate.com>
Quoth Phil Budne:
>NOTE! The ANSI command prefix <ESC>[ will put a real VT52 into "hold
>screen" mode where you need to press some (scroll?) button to allow
>new lines to be added at the bottom of the screen. Ask me how I know!
How do you know?
--
Humm
next prev parent reply other threads:[~2022-01-06 1:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 0:32 Will Senn
2022-01-05 1:35 ` Warner Losh
2022-01-05 1:36 ` Warner Losh
2022-01-05 22:48 ` Will Senn
2022-01-05 15:26 ` Will Senn
2022-01-05 15:44 ` Clem Cole
2022-01-05 15:50 ` Clem Cole
2022-01-05 17:12 ` Grant Taylor via TUHS
2022-01-05 17:28 ` Clem Cole
2022-01-05 17:34 ` Phil Budne
2022-01-05 18:22 ` Will Senn
2022-01-05 19:02 ` Warner Losh
2022-01-05 20:13 ` Will Senn
2022-01-06 1:20 ` Humm [this message]
2022-01-05 1:40 ` Clem Cole
2022-01-06 2:18 ` Jeremy C. Reed
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=YdZD5HHQ3+5K/Z1w@beryllium.local \
--to=hummsmith42@gmail.com \
--cc=phil@ultimate.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).