9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] vt: fix home/end sequences in xterm mode
Date: Fri, 07 Oct 2022 16:12:09 -0700	[thread overview]
Message-ID: <2GETPH4EES84C.3NPA80M8497YY@mforney.org> (raw)
In-Reply-To: <500E574000B68288364FAD993DCA8DAB@eigenstate.org>

ori@eigenstate.org wrote:
> at a guess, our vt220 emulation was written against vt220-old, and we
> never noticed that terminfo changed. We have 2 options: We can update
> our code to match vt220 terminfo, or we can set TERM=vt220-old. Both
> will work (and having home/end keys seems nice).

FWIW, this change happened in ncurses 5.1 from 2000, which predated
the addition of home/end in vt by 17 years.

I was informed off-list that the VT220 keyboard (LK201) has no
home/end keys. Seems to me that the terminfo is correct and they
should be removed from vt220fk.


      parent reply	other threads:[~2022-10-07 23:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 17:34 Michael Forney
2022-10-07 18:14 ` ori
2022-10-07 18:36   ` hiro
2022-10-07 18:49     ` ori
2022-10-07 21:11       ` hiro
2022-10-07 21:56         ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-10-07 23:12   ` Michael Forney [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2GETPH4EES84C.3NPA80M8497YY@mforney.org \
    --to=mforney@mforney.org \
    --cc=9front@9front.org \


* 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).