rpwoodbu / mosh-chrome

Mosh for Chrome
GNU General Public License v3.0
371 stars 59 forks source link

Eating escape sequences #34

Closed shirro closed 10 years ago

shirro commented 10 years ago

I had a weird issue with arrow escapes occasionally (but not always) being eaten and I thought it was something server side with tmux or vim or something but it only happens using mosh-chrome.

I wondered if it was something in hterm or something with mosh in general bit it doesn't happen using Chrome Secure shell to ssh or when using Chrome Secure Shell to do mosh from a local chroot. In all cases TERM is set the same.

rpwoodbu commented 10 years ago

Interesting. I use tmux and vim all the time and haven't witnessed this. How often does it happen? What OS are you running (probably Chrome OS since you mention a local chroot), and what version? What is the observed behavior (e.g., does it just ignore the whole sequence, or does it output a partial sequence as garbage)? And what version of Mosh for Chrome is running? (If it is left running, it can't update.)

shirro commented 10 years ago

It is from a Chromebook to a remote VPS. I thought I had messed up the config on the server initially. Perhaps I still have but it seems to be triggered using mosh so I will keep investigating.

And it is with the latest version I just checked. I have been hacking my own using a hterm with powerline fonts embedded so I made sure I was using the latest official.

And it only happens occasionally and mainly in vim. I really should just disable the arrow keys and move back to hjkl but sublime got me lazy.

shirro commented 10 years ago

Sorry, it wasn't mosh-chrome that was the problem. I liked some of Tim Popes vim plugins and I added vim-sensible for no particular reason and didn't realise it set the timeout value to something ridiculously small. When I had tried to set the timeout myself to debug the problem it had over-ridden my settings, adding to my confusion.

Mosh-chrome must be slower enough than straight ssh or a "native" mosh that vim was seeing the esc as separate to the rest of the key sequence on occasion due to the ridiculously low timeout.