- DIFFERENCES BETWEEN XTERM AND PTERM HOW TO
- DIFFERENCES BETWEEN XTERM AND PTERM FULL
- DIFFERENCES BETWEEN XTERM AND PTERM WINDOWS
> that can be a little more flexible (to make it easier to eventually > patching up and extending the system terminfo, I'm just wondering if :) But since Vim is already in the business of > I'm also aware this all sucks and ideally everything should come from :) But since Vim is already in the business of patching up and extending the system terminfo, I'm just wondering if that can be a little more flexible (to make it easier to eventually upstream things like this into the real terminfo database).
DIFFERENCES BETWEEN XTERM AND PTERM FULL
I'm also aware this all sucks and ideally everything should come from terminfo, full stop. Realistically, Vim's defaults work well for most things that are xterm-like, with only an override or two needed, so it'd be lovely if I could say to Vim "use your builtin termcap for your extensions, but respect the system termcap for my actual terminal otherwise".
DIFFERENCES BETWEEN XTERM AND PTERM HOW TO
But I'm trying to figure out how to make that work well with Vim's builtin termcaps, which set extensions for various things that are not standardized in upstream terminfo yet. In general, I'm all for setting $TERM to a "truthful" setting and filing bugs/sending patches to get the system terminfo database up to date. So it seems to run at cross purposes to the desire that different terminals should have different terminfo and not claim to be xterms.
DIFFERENCES BETWEEN XTERM AND PTERM WINDOWS
It also means that non-Vim apps in :terminal windows will see $TERM=xterm-color and not $TERM=mintty. It works for my particular problem today, but I believe the set term=xterm-color will overwrite any differences between mintty's own (system) terminfo and xterm's. Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread. IMO, treating tmux like an xterm will be positive for almost all users, and the few folks who use tmux with an underyling terminal that isn't compatible with xterm are probably going to have a bad time regardless of what Vim does. tmux's terminfo entries are basically screen's, but with more xterm features. However, I'm not sure this is really a problem in practice. Unlike screen, tmux doesn't seem to have the ability to pass through the underyling terminal's $TERM (e.g., there is no tmux.xterm-256color terminfo like there's a screen.xterm-256color one). It should be trivial to include tmux in the vim_is_xterm function, but I wanted to check that this was sane first. You can work around this by setting tmux's $TERM to screen-256color, but this causes other problems since tmux's own terminfo has diverged from screen long ago. Likewise, bracketed paste doesn't work without manually setting the relevant four termcap codes in your own Vim configuration. For example, t_RV isn't set, and so v:termresponse doesn't get populated. Without Vim detecting tmux as an xterm-like terminal, things mostly work, but any non-standard Vim termcap extensions are not set, even though tmux actually supports (most of?) them. However, tmux's $TERM strings (e.g., tmux-256color) are not currently included in this list, although tmux also emulates an xterm-like terminal. Right now this includes xterm, rxvt, screen (when $TERM is set to something like screen.xterm-256color), and a couple other terminals. Vim uses vim_is_xterm to determine if the terminal is one for which the builtin xterm termcap should be applied.
0 kommentar(er)
