Closed Jeansidharta closed 1 year ago
Should we make this options's default to true
? I think this is way nicer than displaying raw character bytes, and maybe it's not really a breaking change?
@AckslD All done! I've already ammended the commit, so we won't have to squash it
Let me know if there is something else that needs to be changed
@Jeansidharta I just saw the comments above that I thought I had sent was still pending, sorry for that!
Hey @AckslD not a problem! I've been using my own branch of this project for so long that I also forgot this was still open :P
Closes #98.
Macros will now be shown as a proper string that can be used in a
map
, instead of showing the raw byte representation of the keycodes.An example: what would be previously shown as "one\ntwo" will now be shown as "onetwo"
A new options
disable_keycodes_parsing
was added that if set totrue
(dafaultfalse
), will disable this feature, and revert to the old behaviorThis option will only change how macros are displayed, and not how they are stored.
Here's a usage example:
Here's a macro:
Editing the macro (pressed
<C-E>
):After editing the macro, but before closing the edit buffer:
After editing the macro:
After replaying the macro (pressed
<C-Q>
):