-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh + tmux + vim/less $TERM problems #643
Comments
Hello @jeskowagner 👋 Whats' your OS? In any case, you can edit your
|
Thanks for your quick response and sorry for not including more info in the first comment. My OS is Scientific Linux, which is essentially CentOS 7.
Restoring the call to |
Ah yeah I've seen broken Ah sure |
And maybe it's worth reporting to Conda that the |
Closing as now reported in this issue. Thanks again for your swift help! |
Hi and thank you for these dotfiles!
I love them already, but had some troubles around
$TERM
. My setup isssh
>tmux
(v. 3.3). Then, usingless
(orvim
) produced some warnings and errors.E.g.
less
givesWARNING: terminal is not fully functional
andvim
:E437: terminal capability "cm" required
.On the host machine (before tmux),
$TERM
isxterm-256color
. Within the tmux session it'stmux-256color
.Forcing
$TERM
toxterm-256color
fixes the problem. Presumably$TERM
is changed during a call to_apply_tmux_256color
. Indeed, commenting out the call to_apply_tmux_256color
in.tmux.conf
fixes the problem too.$TERM
remains atscreen-256color
this way (as dictacted by.tmux.conf
's lineset -g default-terminal "screen-256color"
)I was wondering what might be causing this problem and what the cleanest way to circumvent it is (for now I am sticking to removing the call to
_apply_tmux_256color
.Best,
Jesko
The text was updated successfully, but these errors were encountered: