From: Will Senn <will.senn@gmail.com>
To: Phil Budne <phil@ultimate.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] vi on v7
Date: Wed, 5 Jan 2022 12:22:55 -0600 [thread overview]
Message-ID: <c121396d-24e9-f513-73a9-2789ea5756d6@gmail.com> (raw)
In-Reply-To: <202201051734.205HYqeq042817@ultimate.com>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
On 1/5/22 11:34 AM, Phil Budne wrote:
> Will Senn wrote:
>> so then I tryed vt50 and vt52 modes...
> xterm should have VT52 emulation, at least the man page on my system says:
>> o VT52 emulation is complete.
> But looking at CTRL+{LEFT,MIDDLE,RIGHT}_CLICK menus didn't show a toggle.
>
> The VT100 sequence to enter VT52 mode seems to be <ESC>[?2l
> you should be able to send it with echo.
>
> Then <ESC>H<ESC>J should clear the screen.
>
> 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!
>
> phil
Well, is there no end to fascination... That 'worked' in that I was able
to do this in n xterm on my mac:
printf "\033[?2l"
which changed the size of the xterm window to 80 chars wide... then:
printf "\033H\033J"
which cleared the screen as you said it would.
But, then, I telnet'd into the the v7 instance and set TERM=vt52, etc.
Now vi gives this:
Y7 HJY- ~
~
~
~
~
~
~
~
~
~Y,
However, I should note that v7 doesn't seem to process escape sequences,
either with a pristine instance or my fully configured instance...
echo '\033'
\033
$ ed test
?test
a
<ESC>J (just echoes the J)
.
w
3
q
$ od -c test
0000000 033 J \n \0
0000003
[-- Attachment #2: Type: text/html, Size: 2981 bytes --]
next prev parent reply other threads:[~2022-01-05 18:23 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 [this message]
2022-01-05 19:02 ` Warner Losh
2022-01-05 20:13 ` Will Senn
2022-01-06 1:20 ` Humm
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=c121396d-24e9-f513-73a9-2789ea5756d6@gmail.com \
--to=will.senn@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).