-
Notifications
You must be signed in to change notification settings - Fork 28k
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
mini.surround
prevents standard vim s
(Substitute) from working.
#1328
Comments
Hey @sbc100! |
Wait, so if you you want to replace the character under the cursor with For me that doesn't work unless I comment out |
yeah, I can do that. I think the issue you are facing is cuz of an older version of which-key - source |
Interesting, I don't have which-key install at all (AFAICT). How is it supposed to work if I type Can you type |
ohh yeah, typing at normal speed doesn't seem to work. Have you tried this solution? |
Yeah so many plugins want to overwrite "s", for surround/substitute/jumping around etc, because "s" is a very ergonomic position whose functionality can easily replaced by "cl" or "xi", you can configure it to vim-surround style keymap though. |
First of all, thanks for all the great work here. This project made my conversion to neovim (after 25+ years or vim usage) very smooth and educational.
After using kickstart to get started with neovim it was pretty surprising to me that find this basic editing command no longer working. I'm not sure if this should be considered a bug in the default bindings of nvim-surround (that repo doesn't seem to have bug reports enabled anyway)? Maybe the users of that plugin all either don't care about this vim feature, or override the default mappings?
Regardless, it does seem a little odd to install a plugin the breaks some fairly core vim behaviour as part of kickstart. Perhaps that one line of init.lua could be removed or commented out:
require('mini.surround').setup()
?Again, thank you. This was really the only wrinkle/surprise I had to deal with.
The text was updated successfully, but these errors were encountered: