You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, Thank you for the great plugin. Love it!
Consider that we have the following maps:
:Arpeggio inoremap th the
:Arpeggio inoremap tha that
If I only have the first map, all works fine. Once I add the second one, there seems to be a conflict and the first map no longer works. I've seen multiple such conflicts when the maps have shared keys.
The text was updated successfully, but these errors were encountered:
Thank you for the report. As you described, such mappings (one is a subset of the other) basically doesn't work because of conflict. Internally,
the first one maps t and h to recognize whether two keys (t and h) are simultaneously pressed, and
the second one maps t, h and a to recognize whether three keys (t, h and a) are simultaneously pressed.
The point is that the second one overrides t and h, so that the example doesn't work.
(If the second one consists of two keys (like Arpeggio inoremap ta ...), it doesn't conflict with the first one.)
As a workaround, reorder mappings by lhs length. For example,
First of all, Thank you for the great plugin. Love it!
Consider that we have the following maps:
:Arpeggio inoremap th the
:Arpeggio inoremap tha that
If I only have the first map, all works fine. Once I add the second one, there seems to be a conflict and the first map no longer works. I've seen multiple such conflicts when the maps have shared keys.
The text was updated successfully, but these errors were encountered: