-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Alt maps break macros and mappings that use <esc> + char #13
Comments
Huh, didn't think about that. Is it true of |
Good thinking - so |
Just ran into this myself. If there is no solution, perhaps a short note in the README.md would be a good idea? |
same here, noticed that my macros were broken, and after a binary search through all the plugins, disabling vim-rsi made it work. |
Note that Neovim doesn't have the meta-macro problem mentioned here. If rsi.vim decides to disable this, I suggest making it conditional on |
rsi already has a flag to disable this, so that works (and its fine for nvim, since folks can do has("nvim") in their vimrc if they want to set that flag conditionally). what would be cool is if we could get vim-rsi meta bindings in vanilla vim (although I guess I might as well switch to neovim already...) |
Ok, but presumably the intention of this issue is to suggest that the meta-maps be disabled by default. They should not be disabled for Neovim. |
Hey, Meta maps in vim-rsi are defined and work for a) insert and b) command line modes. The issue with macros happens only for a) insert mode. Maybe the best approach would be:
[blatant promotion of another plugin - feel free to delete if it's a problem] |
I'm still not clear on why |
@tpope But AFAIK, it doesn't help to make macros work, in particular macros where you use I am happy to provide a simple broken macro example if it helps, it turns out these macros happen a lot, since for instance you might want to edit some text, then leave insert mode ( |
Oh, bleh, didn't catch the part about macros. I guess nuking the insert mode mappings entirely would be fine. |
Closes tpope#13 The CursorHoldI event isn't triggered during macro execution, even when updatetime is set to zero. We can use this 'feature' to create mappings on the CursorHoldI event only when the user manually enters Insert mode.
I just disabled all my plugins one by one to find out which one was messing with macros. Why hasn't #30 been accepted yet? |
Same issue here. Nuking the insert mode mappings doesn't seem to do the trick, as @tpope suggested. Instead, it's lines 57-58 that seem to be causing the issue for me:
My macro register:
Any suggestions? |
Try the pull request @jsit; it worked for me. |
Hi,
for the past week or so I was obsessed with setting up Alt mappings for all the possible keys based on the example provided in vim-rsi. I digged the idea of being able to use Alt as another modifier key. I even created a plugin that enables that (it's a work in progress, but I probably won't bother to finalize it).
Since then, I've learned that setting up alt mappings breaks 2 other things:
esc
+ character andesc
+ charHere's how the issues can be reproduced in vim-rsi:
istuff^[f.astuff^[
.f.
does not do what it should because ^[ + f is recognized asimap <C-s> <Esc>ddi
(this example is obviously made up)Basically, anytime
<Esc>
+ b, d, f, n or p (alt mappings from vim-rsi) is executed in a macro or a mapping, I think it won't work. And it will be dang hard to debug why.For me personally, the biggest issue are
f
andn
because they are used all to often in macros.Not sure if there's any solution to this, but I hope bringing this up helps.
The text was updated successfully, but these errors were encountered: