Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
a bug in vim plugin #3
@viewsafe - Great catch! We'll fix this right away. Can you please let us know which vim plugin you are using since different ones utilize different vs code modes? If you can provide us the plugin you are using we'll try and fix this so that auto end honors the normal mode of that specific vim plugin.
vscodevim, link is:
I'm not very sure if that is a bug. I noticed that the previous version before you add 'colons' funcation, it's same. in vim normal mode once you press ';', a semicolon will appear no matter which vim mode been selected. maybe it's not a bug.
I'm asking this is becasue there is a 'easy motion' founciton in this vscodevim plugin, for example if you using the +s +(char) to search some character , it will help you quick locate the char you are seaching, but sometimes, the found char will apprear a sign like';b', it will help the user quickly locate to there once you press the ';+b'. however, when using Autoend, it will key in a ';' instead of locating to the found character.