From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] vt: fix home/end sequences in xterm mode
Date: Fri, 7 Oct 2022 20:36:28 +0200 [thread overview]
Message-ID: <CAFSF3XNiVN+7bUo885OHH7CVZDUyDXXuMV8U-UH4sc2sOEQgdg@mail.gmail.com> (raw)
In-Reply-To: <500E574000B68288364FAD993DCA8DAB@eigenstate.org>
> 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.
i think vt isn't based on xterm.
anyway, it was also demonstrated that some "bugs" people claimed to
have found that made them prefer st (and it's slightly different
bugs), came from using weird terminfo, too.
next prev parent reply other threads:[~2022-10-07 18:38 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 [this message]
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=CAFSF3XNiVN+7bUo885OHH7CVZDUyDXXuMV8U-UH4sc2sOEQgdg@mail.gmail.com \
--to=23hiro@gmail.com \
--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).