Luckily I discovered/remembered (from real vim) that using Ctrl + [ can send the Esc sequence directly, which is crucial since I left my physical Esc key mapped to the Search functionality since I still frequently use the Ctrl key at the bottom left of the keyboard when switching tabs using Ctrl + PgUp/PgDn.
I've also noticed some really weird interactions with ctrl2esc enabled like sometimes I'll be typing into an input field and the keyboard stops printing every character, but if I hit the Search/Ctrl mapped key to send Esc suddenly it will output some of the missing characters but in a jumbled order from what I had typed. I'll see if I can find a specific sequence that triggers this behavior and if it happens in other places than just this text field.
The really nice thing I forgot to note above is that since the Search key is mapped as Ctrl the Ctrl + [ isn't a very far reach since I can use Search + [ to get the "Esc" alternative.
Luckily I discovered/remembered (from real
vim
) that using Ctrl + [ can send the Esc sequence directly, which is crucial since I left my physical Esc key mapped to the Search functionality since I still frequently use the Ctrl key at the bottom left of the keyboard when switching tabs using Ctrl + PgUp/PgDn.I've also noticed some really weird interactions with
ctrl2esc
enabled like sometimes I'll be typing into an input field and the keyboard stops printing every character, but if I hit the Search/Ctrl mapped key to send Esc suddenly it will output some of the missing characters but in a jumbled order from what I had typed. I'll see if I can find a specific sequence that triggers this behavior and if it happens in other places than just this text field.