It shows the default bindings of the active application's shortcuts. However, with KeyCombiner you can also create personal collections of shortcuts and commands. Those are always shown. In these personal collections, you can set whatever bindings and customizations you like. You can quickly build these collections by importing selected(or all) shortcuts from the public collection of an application.
In practice, when I use the lookup and search for a shortcut that I have customized, I will see both the default binding (because it's shown for the active application), and my own binding (because it's in my personal collections).
Sorry if this was confusing. The blog post explains it in more detail and illustrates with animations.
If there was a way to get a user's custom keybindings on all operating systems for a large majority of applications, I would surely do it. Writing configuration parser's for each application+OS pair is not feasible, and would not work for all applications.
However, I think, in practice, you will find that the custom collections are a nice solution to this problem. I use a lot of custom bindings myself. Having the lookup show both my custom binding and the default binding is actually very nice to understand your custom bindings and find combinations where you might be better of with the default.
Comments
Yes and no.
It shows the default bindings of the active application's shortcuts. However, with KeyCombiner you can also create personal collections of shortcuts and commands. Those are always shown. In these personal collections, you can set whatever bindings and customizations you like. You can quickly build these collections by importing selected(or all) shortcuts from the public collection of an application.
In practice, when I use the lookup and search for a shortcut that I have customized, I will see both the default binding (because it's shown for the active application), and my own binding (because it's in my personal collections).
Sorry if this was confusing. The blog post explains it in more detail and illustrates with animations.
that's what I thought. I think it would better work with a system of extendable config parsers to always show relevant nondefault shortcuts
If there was a way to get a user's custom keybindings on all operating systems for a large majority of applications, I would surely do it. Writing configuration parser's for each application+OS pair is not feasible, and would not work for all applications.
However, I think, in practice, you will find that the custom collections are a nice solution to this problem. I use a lot of custom bindings myself. Having the lookup show both my custom binding and the default binding is actually very nice to understand your custom bindings and find combinations where you might be better of with the default.