vim-easyescape VS better-escape.vim

There's another plugin https://github.com/zhou13/vim-easyescape which does the same but was started in 2017. Yours was on 2020.

This issue is only cosmetic as the other commenter explained. vim won't insert the character until you indicate you're not invoking the keymap (either by waiting or by typing other characters).

If you want a plugin that makes it so that the j appears immediately regardless of whether you're trying to invoke the keymap or not, you can use something like https://github.com/nvim-zh/better-escape.vim

better-escape is what you need then. One tiny plugin, one line of config in your vimrc/init file, and the delay is gone.

Then I came across better-escape.vim, a very recent plugin that does exactly what I want. With core implementation of less than 100 lines of vimscript, it is much more reasonable. People who have better things to do would probably stop here and be content with this perfectly good plugin, but not me. Although the plugin gets the job done, it essentially accomplishes a one-line functionality that is imap jk . For such a simple functionality like this, we really shouldn't be relying on plugins. I want something ultra-simple, something ultra-compact, something that can be put directly into your .vimrc.

Not used this but seem people say it's useful for this usecase https://github.com/jdhao/better-escape.vim

Hi, fellow reditters, I am the author of better-escape.vim, which is created about 9 months ago. In fact, I have announced it in my eariler post.

You can use the plugin better-escape.vim'.

I have used the plugin https://github.com/jdhao/better-escape.vim

Ok so I apologize if this isn’t super helpful, but I remember reading this about how to write a function to map jk to escape without having that annoying lag you talk about. You could maybe use this same approach but alter it a bit to make two spaces turn into an underscore but without lag. The author of that post also made a plugin with that idea, so maybe it could help you?