Grégoire Geis

There was indeed an issue where a reload was needed for your second example to work (fixed in 9e3bbe9c3052c84b5e8c2167637f674f789cb17c), but your first example works fine for me.

This is a good idea. With your additions to the wiki recently I'm been thinking more and more about how we can start adding optional (and easy to enable) key...

I don't know if other extensions do it, but being used as a library is an explicit goal of Dance. I also didn't want actions to be assigned to keys,...

I'm not sure I understand. The fact that right now we don't override the `type` command by default should not cause conflicts with LeaderMode (and that's the one significant advantage...

@tshort Oh I see now, my bad. If we override `type`, then we'll definitely have conflicts. The problem here is that the `normal` Dance keybindings take precedence over `type` when...

@yuchenshi The first point is valid and I often think about it. We would either have to add keybindings that do nothing for the rest of the keys or not...

Not really sure what happening, but thank you for investigating! I can't try to troubleshoot right now, but something you could try is opening the dev tools in VS Code...

1. It is technically possible to implement this, but I'd rather not. Status bar color changes can only be implemented by updating VS Code preferences, which is slow, but more...

No. Different commands have different default registers, and some of them use the `"` register which is mapped to the clipboard. In theory we could add a preference to disable...

Hey there! The way you created a menu is correct, and the way to add commands is indeed to add VS Code keybindings. However, the fact that `c` is printed...