Sometimes pressing Esc key will take a long time to get response.
The reliable way to reproduce it is:
vimi into insert modetest<Esc> key to leave insert mode. It will take roughly a second.:q! to leave vim<Esc> key still take a while to register. Random typing anything and <Esc> key will take a while to clean the cmd command line.Reload won't fix it, only full reload with Ctrl-Shift-F5 can reset this behavior.
I can reproduce this issue in the demo app of xterm.js.
Looks like an upstream issue
Am also getting this issue
Testing the terminal timeout tweak in this post seems to fix this. I am only getting this issue when ssh'd to outside servers. This only popped up recently, it's been working fine for a while.
I get this too - but not when I first open a terminal and SSH out. It happens over time.
I'm using WSL as my base shell
This also happens to me over time.
I love Hyper - it's the best terminal experience I've found for Windows.
This is pretty much a deal breaker for me though.
I end up eventually finding myself pounding ESC over and over again in VIM
trying to get out of insert mode :(
On Wed, Nov 21, 2018 at 11:29 AM Adam Hopkins notifications@github.com
wrote:
This also happens to me over time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zeit/hyper/issues/2922#issuecomment-440480358, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABKRoxNbeZ3aHDDP9_Vs4y3E-ephPw6Bks5uxJ5pgaJpZM4ThBkq
.
I have the same issue.
I have never used hyper, but just for information I can share that I'm having similar problem with ESC taking about 1 second to register.
My setup is: WSL (Windows Subsystem for Linux) with Ubuntu -> ssh -> tmux -> nvim
I have never used hyper, but just for information I can share that I'm having similar problem with ESC taking about 1 second to register.
My setup is: WSL (Windows Subsystem for Linux) with Ubuntu -> ssh -> tmux -> nvim
Not clear if this is on hyper or ubuntu.exe?
@LexSong @ecielam @jamessewell @uadev
Is it still happening?
Can you try out the ci build once also (lots of improvements since last release)
I had this issue and narrowed it down to a tmux config problem:
Fix it by adding set -sg escape-time 0 to ~/.tmux.conf
You can apply it without restarting tmux by:
<C-b>:source-file ~/.tmux.conf (or substituing <C-b> for your tmux control key)
@LexSong @ecielam @jamessewell @uadev
Is it still happening?
Can you try out the ci build once also (lots of improvements since last release)
Hi, sorry for the late reply
I can confirm that this issue no longer exists.
I'll close this issue.
Most helpful comment
I can reproduce this issue in the demo app of xterm.js.
Looks like an upstream issue