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
I've often looked at this package and wondered why it seems very nearly useful.
The lack of data on key sequences seems to be a problem.
Implementation wise, for each command, we can just take the most recently seen sequence to be the sequence that binds the command.
This would only wildly alternate for commands we're not usually interested in, such as self-insert-command.
As a follow-up, it would be preferable if we could group commands by key sequences and thereby see which keys we use the most, aggregated over the commands the same sequence dispatches to.
The text was updated successfully, but these errors were encountered:
I've often looked at this package and wondered why it seems very nearly useful.
The lack of data on key sequences seems to be a problem.
Implementation wise, for each command, we can just take the most recently seen sequence to be the sequence that binds the command.
This would only wildly alternate for commands we're not usually interested in, such as self-insert-command.
As a follow-up, it would be preferable if we could group commands by key sequences and thereby see which keys we use the most, aggregated over the commands the same sequence dispatches to.
The text was updated successfully, but these errors were encountered: