Yep, works perfectly. Thanks for this -- I missed this. Much appreciated.
On Wed, Apr 10, 2013 at 6:45 AM, Ashwin G wrote:
> Vim understands the xterm style key sequences when the TERM variable is
> set to xterm*. But since tmux sets it to screen instead, vim fails to
> recognize these keys.
A job's bufferevent has EV_WRITE enabled by default, but libevent
internals prevent the job_write_callback from being invoked unless
we do (at least one of):
- call bufferevent_enable with EV_WRITE, or
- call bufferevent_write with non-zero length data
Either of these will enable the internal
Vim understands the xterm style key sequences when the TERM variable is set
to xterm*. But since tmux sets it to screen instead, vim fails to recognize
these keys. But this is easily fixable (and should be documented in the man
page if not already done IMO).
First, you need to enable the xterm-key
The default VIM key sequence to navigate to the previous/next tab is
C-PageUp and C-PageDown, respectively. It appears that these sequences do
not work under either tmux 1.5 or 1.6, and I've tried under Centos as well
as Ubuntu. I tried unbinding the sequence in my .tmux.conf, but that had no
effec
A while back I created a thread about tmux sending garbage characters to
screen when a click would occur past 220 characters in the terminal while
using Putty and some other terminals. Nicholas noted that the issue was not
with tmux but due to the terminal itself not supporting extended mouse mode
