Configuring function keys in PuTTY for both Vim and Midnight Commander under tmux?
--------------------------------------------------
Hire the world's top talent on demand or became one of them at Toptal: https://topt.al/25cXVn
and get $2,000 discount on your first invoice
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Beneath the City Looping
--
Chapters
00:00 Configuring Function Keys In Putty For Both Vim And Midnight Commander Under Tmux?
02:32 Accepted Answer Score 8
03:06 Thank you
--
Full question
https://superuser.com/questions/918580/c...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#vim #keyboard #putty #tmux #midnightcommander
#avk47
Hire the world's top talent on demand or became one of them at Toptal: https://topt.al/25cXVn
and get $2,000 discount on your first invoice
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Beneath the City Looping
--
Chapters
00:00 Configuring Function Keys In Putty For Both Vim And Midnight Commander Under Tmux?
02:32 Accepted Answer Score 8
03:06 Thank you
--
Full question
https://superuser.com/questions/918580/c...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#vim #keyboard #putty #tmux #midnightcommander
#avk47
ACCEPTED ANSWER
Score 8
The problem is the TERM=xterm outside tmux. There is no configuration of PuTTY which matches the xterm terminal description, and the mismatch feeds into screen or tmux (take your pick).
See for example, in the ncurses FAQ Why not just use TERM set to "xterm"?. The recommendation there is of course to set
TERM=putty
A quick check using tack shows that this combination (TERM=putty, tmux) works for Ubuntu 14.04 (you should have installed the ncurses-term package, which includes this).