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
Common confusion was that plain keys in leader translate to C-<key>
when in reality the tutorial meant this only applies to plain keys
AFTER a prefix. Hopefully this context-dependent ambiguity has been
removed.
Copy file name to clipboardExpand all lines: TUTORIAL.org
+20-12Lines changed: 20 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,24 +88,32 @@ The following keys will act according to following rules:
88
88
89
89
- ~m~ will be translated to ~M-~.
90
90
- ~g~ will be translated to ~C-M-~.
91
-
- ~SPC~ stands for literal prefix, means the next key will not be modified.
92
-
- Any other ~<key>~ will be translated to ~C-<key>~.
93
-
- If the translation results in an undefined binding, the last key will fallback to an unmodified version. (e.g. If ~C-c C-a~ is undefined, fallback to ~C-c a~)
91
+
- Any key following a prefix like ~m~ or ~g~ is interpreted as
92
+
~C-<key>~.
93
+
- ~SPC~ stands for literal prefix, means that the key will not be
94
+
modified with ~C-~.
95
+
- If the translation results in an undefined binding, the last key
96
+
will fallback to an unmodified version. (e.g. If ~C-c C-a~ is
0 commit comments