Is your feature request related to a problem? Please describe.
The purebred-dump-keybindings program involves considerable complexity to initialise the configuration, which is mostly duplicating the main program itself. But there is an important difference: purebred-dump-keybindings does not load user configuration or run config plugin hooks that could result in customised keybindings. So it can only show the default keybindings.
Describe the solution you'd like
Merge this "dump keybindings" behaviour into the main program, triggered by the --dump-keybindings flag
Describe alternatives you've considered
nil
Additional context
This also has the nice effect of having fewer programs to update when API changes, and the exe:purebred-dump-keybindings build target will be no more (so it cannot be missed accidentally).
Is your feature request related to a problem? Please describe.
The
purebred-dump-keybindings
program involves considerable complexity to initialise the configuration, which is mostly duplicating the main program itself. But there is an important difference:purebred-dump-keybindings
does not load user configuration or run config plugin hooks that could result in customised keybindings. So it can only show the default keybindings.Describe the solution you'd like Merge this "dump keybindings" behaviour into the main program, triggered by the
--dump-keybindings
flagDescribe alternatives you've considered nil
Additional context This also has the nice effect of having fewer programs to update when API changes, and the
exe:purebred-dump-keybindings
build target will be no more (so it cannot be missed accidentally).