The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mary Ann Horton <mah@mhorton.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Compatibility question
Date: Sun, 17 Dec 2023 14:51:00 -0800	[thread overview]
Message-ID: <76f6ae7e-20e1-41fa-9fe4-cc22015411bf@mhorton.net> (raw)
In-Reply-To: <kN4q4JyK0llkf4XE1pDQNZjCF_MYz1ditOGTCH4nikqXLc4PlI_saNQ_KhRRyVlx7vVOsphLzywcN0ssNsI_HsQ2RoBT70uE5m6DQy1lUMQ=@protonmail.com>

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

The concept of a resizable window didn't appear until GUI interfaces. 
Originally the hardware terminal had one specific size and vi depended 
on the screen being that exact size. I suspect that SVr2 was in that 
category, as the Sun merger of SVr4 would have been the reason to 
incorporate it. So try a 24x80 window and see if it behaves.

Try "stty -a" and see if it mentions rows and columns. If not, what 
terminfo says (try "infocmp") is what vi will believe.

It might also matter how you option your vt100 emulator, and even the 
native vt100 had setup options, such as wraparound (terminfo calls this 
auto_right_margin or just am). Vi depends on knowing what the cursor 
does when it types in the rightmost column.

Thanks,

/Mary Ann Horton/ (she/her/ma'am)
maryannhorton.com <https://maryannhorton.com>



On 12/17/23 10:23, segaloco via TUHS wrote:
>> On 12/16/23 6:01 PM, KenUnix wrote:
>>
>>> I have been working with a VAX780 sim running
>>> Unix System V r2 VAX780 and am having strange
>>> issues.
>>>
>>> TERM is defined at vt100
>>>
>>> When firing up vi at times the cursor is positioned
>>> in the wrong place or when inserting text it over
>>> writes areas on the screen.
>>
>> I have most often encountered this when my terminal window size was
>> larger than exactly 80x24.
>>
>> If you're using Xterm or Gnome-terminal or a Windows terminal, for
>> example, make sure that the window is exactly 80 columns wide by 24
>> lines tall, or the VT100 termcap inside the emulator will be very confused.
>>
>> -Seth
> I'm not so sure on that one, I ran this on an arbitrarily sized xterm (I use a tiling WM) and it sized the vi session correctly and didn't seem to exhibit cursor anomalies.  This encapsulating terminal is a recent (past year) build of xterm using I believe the xterm256 or whatever its named TERM, in which I then launched your script using my local copy of vax780.  Tried just now in Linux fbcon with a TERM of "linux" and likewise the vi session still seems to size to 80x24 appropriately and doesn't have any cursor positioning issues.  Note in both cases the TERM variable I describe is the *host* terminal, TERM in the emulated session is vt100.
>
> - Matt G.

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

  reply	other threads:[~2023-12-18 16:29 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17  2:01 [TUHS] " KenUnix
2023-12-17 18:13 ` [TUHS] " Seth Morabito
2023-12-17 18:23   ` segaloco via TUHS
2023-12-17 22:51     ` Mary Ann Horton [this message]
2023-12-17 22:59       ` Ron Natalie
2023-12-17 23:08         ` Warner Losh
2023-12-18  0:35           ` KenUnix
2023-12-18  3:24             ` segaloco via TUHS
2023-12-18 17:05         ` Paul Winalski
2023-12-18 22:29           ` Jon Forrest
2023-12-19  1:46           ` Dave Horsfall
2023-12-19  7:56             ` Harald Arnesen
2023-12-19 17:40             ` Paul Winalski
2023-12-19 18:07               ` Tom Lyon
2023-12-19 20:23                 ` Clem Cole
2023-12-19 21:31                   ` Paul Winalski
2023-12-19 23:52                     ` Bakul Shah
2023-12-20  0:05                       ` Greg 'groggy' Lehey
2023-12-20  1:03                         ` Bakul Shah
2023-12-20  1:32                           ` Greg 'groggy' Lehey
2023-12-20  6:05                             ` Wesley Parish
2023-12-20  0:15                       ` Mary Ann Horton
2023-12-20 16:07                         ` Adam Thornton
2023-12-20 16:22                           ` Clem Cole
2023-12-20 18:11                           ` Alan D. Salewski
2023-12-20 16:34                         ` Paul Winalski
2023-12-20 18:15                           ` Jon Forrest
2023-12-20  1:11                       ` Steffen Nurpmeso
2023-12-20  1:23                         ` Tom Lyon
2023-12-21  3:53                     ` Rod Bartlett via TUHS
2023-12-19 21:34                   ` Rob Pike
2023-12-17  5:55 David Arnold
2023-12-17  8:08 ` segaloco via TUHS
2023-12-17 18:04   ` James Frew
2023-12-17 18:18     ` Lars Brinkhoff
2023-12-17 19:14       ` Brad Spencer
2023-12-17 18:48     ` Paul Winalski
2023-12-17 18:59       ` Warner Losh
2023-12-17 20:24       ` Dave Horsfall
2023-12-17 19:26     ` Dan Cross
2023-12-17 20:08       ` Warner Losh
2023-12-17 14:07 ` Brad Spencer
2023-12-17 14:47   ` Arrigo Triulzi via TUHS

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=76f6ae7e-20e1-41fa-9fe4-cc22015411bf@mhorton.net \
    --to=mah@mhorton.net \
    --cc=tuhs@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).