9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] vt: fix home/end sequences in xterm mode
Date: Fri, 07 Oct 2022 14:14:11 -0400	[thread overview]
Message-ID: <500E574000B68288364FAD993DCA8DAB@eigenstate.org> (raw)
In-Reply-To: <1132EA054DF091104D293E57741F6906@mforney.org>

Quoth Michael Forney <mforney@mforney.org>:
> 
> According to the ncurses terminfo database, we have
> 
> $ for k in khome kend; do printf '%s:\t' $k; TERM=xterm tput $k | od -An -tc; done
> khome:	033   O   H
> kend:	033   O   F
> $
> 
> This differs from vt220fk, so add a new xtermfk table with the proper
> sequences.

Looks good to me.
> ---
> I also noticed that the vt220 definition in ncurses terminfo does not
> have khome/kend entries, and instead maps the sequences \033[1~ and
> \033[4~ to kfnd (key_find) and kslt (key_select), so home/end don't
> work with -2 either. However, there is a "vt220-old" definition that
> maps them to the same sequences as in the vt220fk table. I'm not a
> terminal expert so I don't know which is correct, but just thought I'd
> mention it in case someone knows.

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

k0ga is our resident terminfo expert, though, and probably has a better
idea of what to do.

Also, on a related note -- an idea floated was to make vt compatible with
st instead of xterm, either via lifting their rendering code and porting
it, or via incremental changes. This would hopefully fix a bunch of quirks
and rendering issues we end up running into.

> 
> diff 7bb34f7d22d90f59eaa3778398ada0b66b0f7b86 e919f465e965129ef3b14003bff5a9c54dcbe8e7
> --- a/sys/src/cmd/vt/cons.h
> +++ b/sys/src/cmd/vt/cons.h
> @@ -39,7 +39,7 @@
>  	char	*sequence;
>  };
>  extern struct funckey *fk, *appfk;
> -extern struct funckey ansifk[], ansiappfk[], vt220fk[];
> +extern struct funckey ansifk[], ansiappfk[], vt220fk[], xtermfk[];
>  
>  extern int	x, y, xmax, ymax, olines;
>  extern int	peekc, attribute;
> --- a/sys/src/cmd/vt/main.c
> +++ b/sys/src/cmd/vt/main.c
> @@ -286,7 +286,7 @@
>  			sysfatal("could not create log file: %s: %r", p);
>  		break;
>  	case 'x':
> -		fk = vt220fk;
> +		fk = xtermfk;
>  		term = "xterm";
>  		break;
>  	case 'r':
> --- a/sys/src/cmd/vt/vt.c
> +++ b/sys/src/cmd/vt/vt.c
> @@ -91,6 +91,35 @@
>  	{ 0 },
>  };
>  
> +struct funckey xtermfk[] = {
> +	{ "insert",		"\033[2~", },
> +	{ "delete",		"\033[3~", },
> +	{ "home",		"\033OH", },
> +	{ "end",		"\033OF", },
> +	{ "page up",		"\033[5~", },
> +	{ "page down",		"\033[6~", },
> +
> +	{ "up key",		"\033[A", },
> +	{ "down key",		"\033[B", },
> +	{ "left key",		"\033[D", },
> +	{ "right key",		"\033[C", },
> +
> +	{ "F1",			"\033OP", },
> +	{ "F2",			"\033OQ", },
> +	{ "F3",			"\033OR", },
> +	{ "F4",			"\033OS", },
> +	{ "F5",			"\033[15~", },
> +	{ "F6",			"\033[17~", },
> +	{ "F7",			"\033[18~", },
> +	{ "F8",			"\033[19~", },
> +	{ "F9",			"\033[20~", },
> +	{ "F10",		"\033[21~", },
> +	{ "F11",		"\033[23~", },
> +	{ "F12",		"\033[24~", },
> +
> +	{ 0 },
> +};
> +
>  char gmap[256] = {
>  	['_']	' ',	/* blank */
>  	['\\']	'*',	/* diamond */


  reply	other threads:[~2022-10-07 18:15 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 [this message]
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

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=500E574000B68288364FAD993DCA8DAB@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.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).