-
Notifications
You must be signed in to change notification settings - Fork 21
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
Error message on space #10
Comments
This was caused by a problem with menu and a mapping. I had a mapping to |
I believe there are two separate, if somewhat related issues here. Both caused by conflicts between native vim mappings and configuration dictionaries. First the error messages. The second point, the [fm] mapping is undoubtedly caused by mapping conflicts, but the way forward is less clear. What you are seeing is the poor man's conflict handling. The fm mapping is an attempt to keep the f-menu accessible even when a conflicting vim mapping exists. And I'd agree, this certainly not the best solution imaginable. It's a remain from when I first tried my hand at those conflicts. As for how to do it correctly, I am still unsure. I will write up some of my thoughts and open another issue on that shortly. |
Alright, that went faster than expected. By default conflicting mappings should now get displayed in the parent menu with a two letter mapping. Notwithstanding this, conflict handling is a mess and could use a rework. |
Thanks for everything! Any remaining concerns are probably best continued in #11 |
Another one of these, this one doesn't stop the menu from showing, but does really slow me down:
I think it doesn't very robustly handle conflicting entries of varying kinds. It's probably worth trying to detect errors like these at various points, and better explain the issue so it can be handled/corrected.
The text was updated successfully, but these errors were encountered: