-
Notifications
You must be signed in to change notification settings - Fork 14
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
Interaction with macros #49
Comments
Can't reproduce, it works as expected for me. |
I tried switching to There could be some third plugin interacting, or perhaps its a timing issue. The fact I get a few different results for the same set of input keystrokes suggests as much. If you're not interested in digging deeper, that's fine. I understand you're strapped for time. |
It happens on vim8, not neovim. |
Interesting. Sounds more and more like performance / racing condition, in my case it's happening with Still, using another plugin for pairs is ok too. There are quite a few coc plugins I can't live without 😅 but this one has good alternatives. Thanks for all the great software! |
Same problem here with NVIM I really like this auto-pairs plugin and I don't want to change... |
The issue is still present. Is there a way to disable the plugin temporarily, before running a macro? |
In help under
So you could run a command, or map toggling it to a keybinding. I just switched to: https://github.com/jiangmiao/auto-pairs
Because this issue reminded me, I've recently been frustrated writing macros again and just saw my advice above to switch 😅 . Another thing one could try is to try and use multi cursor more: |
coc-pairs is damn smart. jiangmiao/auto-pairs is out for me. When writing Rust, auto-pairs by default won't pair On to the next 😬 . |
I was having trouble recording a macro and noticed it appears to be due to the insertion of pairs.
With this extension on running
:normal O('')
produces a list that looks something like the following:Turning it off produces the sequence you'd expect.
It's no biggie, I can turn it off when recording complex macros or use a different plugin but perhaps you do know why this is happening.
The text was updated successfully, but these errors were encountered: