[Windows] ESC key is delayed in vim/neovim #1680
Comments
|
Think part 2 should be a second issue. Got the same problem with norwegian layout. |
niklas88
changed the title
|
@meltinglava I've changed the title and created a new issue (#1681). |
|
Have you tried this already? https://www.johnhawthorn.com/2012/09/vi-escape-delays/ |
|
@Bobo1239 I had not until just now. I wasn't using tmux for which I knew about that setting and had it set. Setting the timeouts in vim and zsh sadly had no effect. |
|
My initial suspicion is that it's caused by this. I must say I don't know a lot about terminal escapes, @chrisduerr is there a way to explicitly send just the escape key without it being potentially recognised as an escape sequence? Otherwise we could reduce that timeout, though that would require changes to the winpty-agent binary, so would have to be changed on winpty's repo. |
|
I'm not aware of any way to send escape other than sending escape. However vim does have a built-in alternative to |
|
If there's no way to 'flush' the input processing in winpty then changing the timeout seems reasonable. This doesn't happen in all terminals using winpty though, I'll take a look at how they handle it. |
zacps
changed the title
|
Changed title because this is caused by winpty, not wslbridge. |
|
@chrisduerr it does still happen with |
|
Relevant mintty docs: https://github.com/mintty/mintty/wiki/CtrlSeqs#escape-keycode |
|
I can no longer reproduce this with the newest Alacritty version on Windows, at least not when using ConPTY. Vim and NeoVim work fine both via ssh and on local WSL. |
|
Great to hear this is resolved by ConPTY, though this issue has already been flagged by @zacps as WinPTY, so he's probably already aware. |
|
I'm seeing this issue even in I have not yet tried installing any additional software. |
|
Same issue here. Need to wait around 1s for ESC or C-[. |
|
i'm also experiencing this |
|
Does anyone have a fix for this? i.e. how can get alacritty to use ConPTY? |
|
If you are up to date with Windows, you just need to set the conpty setting in the config (see default config for docs). |
|
@chrisduerr Hadn't seen that because my For anyone else who doesn't have the option in their |
|
This still doesn't work for me with |
|
@jamessewell Make sure you're using at least version 1809 of Windows 10. Previously the ConPTY interface was not supported yet. |
|
That was it! For some reason I was version pinned on 1803
…On Wed, 10 Apr 2019 at 6:10 pm, Christian Duerr ***@***.***> wrote:
@jamessewell <https://github.com/jamessewell> Make sure you're using at
least version 1809 of Windows 10. Previously the ConPTY interface was not
supported yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1680 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKRo2EbNDJLH53uMnp3_3FP-9JUJvxHks5vfZxrgaJpZM4Xs-uk>
.
|
|
I also found that (1) upgrading to Windows 10 build 1809 and (2) enabling the experimental conpty backend resolved the vim ESC key delay. |
|
For everyone else with the same escape delay problem, I made this simple script to help debug: Run that, and you should see For me, updating to Window 10 Build 1903, and enabling |
|
it seems like after pressing "esc" its waiting for something and goes in a timeout for it, if i immediately press colon key after "esc" it some weird character comes out and when i tried the same thing with other keys some other characters were coming out these are some of it: |
|
@Neelu0 That sounds like the behavior you'd see from remapping `<ctl>-K` to
`<ESC>`, or possibly just from `:set digraph`:
https://vim.fandom.com/wiki/Entering_special_characters
…On Wed, Aug 14, 2019 at 6:45 AM neelu0 ***@***.***> wrote:
it seems like after pressing its waiting for something and goes in a
timeout for it, if i immediately press colon key after it some weird
character comes out and when i tried the same thing with other keys some
other characters were coming out these are some of it:
»ºñ´åòôùçæäöãøö
but when leaving insert mode with Ctrl-C, vim goes to normal mode like
usual.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1680>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARU4T6UFSEMLQRKLWSLIJ3QEP467ANCNFSM4F5T5OSA>
.
|
|
Strangely this has regressed with an updated alacritty and new Laptop on Win 10 1903 Script above shows delay when pushing escape EDIT: The problem was tmux this time! Pretty sure |
|
WinPTY support has been removed. |
Ultimate bruh moment, come on tmux. Thank you for the fix |
This was annoying as shit, vim crawled. See: vim/vim#2872 See: alacritty/alacritty#1680 See: https://www.johnhawthorn.com/2012/09/vi-escape-delays/ See: https://unix.stackexchange.com/a/25638
First thanks to bringing alacritty to Windows! I'm almost exclusively a Linux user but I sometimes need to use Windows (damn those presentation video dongles). Now with alacritty + WSL Windows becomes an at least somewhat usable OS.
I'm using wsl (via
wslbridgefrom wsltty installation 1.9.3)In both
vimandnvimin insert mode I'm seeing a delay between pressing<ESC>and getting out of insert mode. It feels like almost a second. This doesn't happen with wsltty or the garbage built-in thing they call a terminal.The text was updated successfully, but these errors were encountered: