New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a bug in vim plugin #3

Open
viewsafe opened this Issue Apr 4, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@viewsafe

viewsafe commented Apr 4, 2017

In vim normal mode, when you press the key';', a semi-colon will appear. Actually, it shouldn't appear a semicolon in vim normal mode.

@thousandtyone

This comment has been minimized.

Show comment
Hide comment
@thousandtyone

thousandtyone Apr 4, 2017

Owner

@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.

Owner

thousandtyone commented Apr 4, 2017

@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.

@viewsafe

This comment has been minimized.

Show comment
Hide comment
@viewsafe

viewsafe Apr 4, 2017

vscodevim, link is:
https://github.com/VSCodeVim/Vim/releases.

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.

viewsafe commented Apr 4, 2017

vscodevim, link is:
https://github.com/VSCodeVim/Vim/releases.

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.

@viewsafe

This comment has been minimized.

Show comment
Hide comment
@viewsafe

viewsafe Apr 4, 2017

(leader) (leader)+s+(char)

viewsafe commented Apr 4, 2017

(leader) (leader)+s+(char)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment