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. putty-256color putty-256colorĬomparing putty-256color to putty-256color.Vim uses vim_is_xterm to determine if the terminal is one for which the builtin xterm termcap should be applied. For instance between the Ubuntu 20.04 entry (6.2-0ubuntu2 package, 6.2-20200212 upstreams) and the one from 6.2-20201107 above, I see: $ infocmp -A /usr/share/terminfo -B. Note that the entry may change depending on your version of ncurses. Running infocmp -xL putty-256color xterm-256color with that version of ncurses, I get: comparing putty-256color to xterm-256color.Īcs_chars: '``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz%-%d%e38 5 %p1%d% m, So you'll see it includes the base putty definition and the same sequences as xterm for 256 color. (though that 0.58 may be misleading as comments above the putty entry mention 0.71). You can also look at the source definition of those entries in misc/terminfo.src in the ncurses sources or online for the latest version ( PuTTY section). When both are available (after installing ncurses-term on that version of Ubuntu at least), you'll be able to compare xterm-256color and putty-256color with infocmp. ![]() On Ubuntu 20.04 at least, terminfo entries are split between the ncurses-base (included by default) and ncurses-term (not). There's a terminfo entry for putty-256color shipped with ncurses like the rest of the terminfo entries.
0 Comments
Leave a Reply. |