The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] vi on v7
Date: Wed, 5 Jan 2022 14:13:22 -0600	[thread overview]
Message-ID: <3458bd82-0896-1570-8315-00b222d8ca1d@gmail.com> (raw)
In-Reply-To: <CANCZdfomuP80h9w-qaM0DgaivKL+q3RxKd3BUwhisaAU9bMN9A@mail.gmail.com>

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


> There's escape problems :(.  I'll see if I can spin up a V7 box and 
> see if I have any suggestions.
>
> Warner

OK. Here's the update. I set tto 7b in SimH (which is bad?) and ESC 
works. Then in vi, it only uses half the screen. Per Clem's suggestion, 
I ran stty 9600, and voila, it "worked" full screen. Yay!

Now, it's just a matter of getting ex/vi working properly as an editor. 
I can confuse it pretty easy once it's up and running. Either this 
version of vi's got some pretty awful bugs, or I screwed up the build, 
but at least the screen's cooperating better now.

So, is 7b bad and should I be looking for another solution?

Will



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

  reply	other threads:[~2022-01-05 20:14 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 [this message]
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=3458bd82-0896-1570-8315-00b222d8ca1d@gmail.com \
    --to=will.senn@gmail.com \
    --cc=imp@bsdimp.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).