joshuafcole
commented
10 years ago Seems like a good idea. An alternate approach might be to ignore keybinding shifts when the active tab becomes keymapper, so it would work in either case. Issue with that is I don't know if we can detect the change before the keybindings have remapped.
Either way, should definitely do something in-plugin.
On Fri, Apr 4, 2014 at 3:33 AM, Jakub Holy notifications@github.com wrote:
I, as perhaps many others, have fallen into the trap of not opening keymapper in a different tab set. Since people in general do not read documentation, it would be nice to inform them about this in a way they cannot ignore. I think that it would be best, when I open keymapper, it contained at the top a brief text, st. like
Showing binding for the currently active tab. Make sure to open this in a different tab set and then go to the tab you want to see keybindings for.
It would be even better if it could show what file/tab it is showing bindings for.
Reply to this email directly or view it on GitHubhttps://github.com/joshuafcole/keymapper/issues/11 .
Screw the environment. Please print this email immediately. And then burn it.
I, as perhaps many others, have fallen into the trap of not opening keymapper in a different tab set. Since people in general do not read documentation, it would be nice to inform them about this in a way they cannot ignore. I think that it would be best, when I open keymapper, it contained at the top a brief text, st. like
It would be even better if it could show what file/tab it is showing bindings for.