Kovid Goyal wrote:
[...]
> > That is not Vim's doing. You have have some termcap/terminfo entries
> > setup to cause this.
>
> vim is outputting the bytes, so its vim's doing.
So it's Vim's doing for whoever put those codes in terminfo? No, of
course not. Whoever put those codes in terminfo is responsible, Vim
just follows the rules (as well as possible) outputting the codes. Of
course Vim does not know what the bytes mean, that's the whole idea of
using terminfo entries.
> > The terminfo manpage has these entries:
> >
> > enter_ca_mode smcup ti string to start pro‐
> > grams using cup
> >
> > exit_ca_mode rmcup te strings to end pro‐
> > grams using cup
> >
> > You do know about the relation between terminfo and termcap names,
> > right? They are 1:1, so either can be used to identify an entry.
>
> They are not 1:1, terminfo has many capabilities that termcap lacks.
> Some examples:
>
> Sync Tc setrgbf setrgbb fullkbd kUP kDN kbeg kBEG
Looking at "man terminfo", which is the best I have on my system:
- Sync does not exist
- Tc does not exist
- setrgbf does not exist
- fullkbd does not exist
- kUP does not exist
- kDN does not exist
- kbeg does exist, the termcap equivalent is "@1".
- kBEG does exist, the termcap equivalent is "&9".
I'm sure the ones that do not exist in my manpage will exist somewhere,
but I don't really care about them. And giving them a termcap entry
name is just a matter of time. What matters is that the relation is
1:1, if you have the termcap entry name, you can lookup the terminfo
entry name, and vice versa. Some entries may not have both names, but
if they do then it's clear what the relation is.
> If you insist on using termcap/terminfo in vim maybe you should
> educate yourself about them a little.
I find that remark offensive.
> > > te and ti are in termcap not terminfo. And they mean put terminal in
> > > "cursor motion" mode. AKA alternate screen. What are you expecting to be
> > > in ti and te? And does vim really read termcap rather than terminfo?
> >
> > That is irrelevant, they are the same entries.
>
> In which case here you go
[comparing xterm with xterm-kitty]
That is beside the point, I said that the entries from terminfo and
termcap are the same. Unless perhaps you have a system that was badly
configured. I mean, why would they ever be different?
> So I think you can stop blaming kitty's terminfo for this bug.
I was blaming kitty for having a different state, depending on being in
the main or the alternate screen. That is the cause of this bug.
There is some rationale hidden in the keyboard protocol spec (the note
above the "Disambiguate escape codes" section), but it ignores the
problems it introduces. Especially that no existing application can
deal with it, thus introducing a big problem. And I see no good
justification for it.
> You yourself claim ti and smcup are the same. Every terminal under the
> sun has alternate screen in smcup. I demonstrated it above for xterm and
> kitty. Here are some more:
You only mention some fairly recent terminals. Anyway, the problem is
not about switching between main and alternate screen, Vim deals with
that as well as can be expected. The problem is that the switch is not
expected to have an effect on what key protocol is used.
> So let me ask you, where do you get the idea that cursor motion mode
> is *not* alternate screen. And if you think its not, what do you think
> it means?
Eh, just read: "cursor motion mode", "alternate screen". Two completely
unrelated concepts. You are avoiding my question.
--
Apologies for taking up the bandwidth with the apology. Anything else I
can apologise for ...... er no can't think of anything, sorry about that.
Andy Hunt (Member of British Olympic Apology Squad)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20221216164159.D1DBB1C0869%40moolenaar.net.
