if a keybinding is double-used astroid crashes with
ERROR: key: l (thread_view.tag_message) is already user-configured in map with name: thread_view.up
(astroid:28845): glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: key: l (thread_view.tag_message) is already user-configured in map with name: thread_view.up
zsh: trace trap astroid
which is kind of ugly. a tolerant behaviour or an early reject of the config at startup would be much appreciated.
if a keybinding is double-used astroid crashes with
ERROR: key: l (thread_view.tag_message) is already user-configured in map with name: thread_view.up
(astroid:28845): glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: key: l (thread_view.tag_message) is already user-configured in map with name: thread_view.up
zsh: trace trap astroid
which is kind of ugly. a tolerant behaviour or an early reject of the config at startup would be much appreciated.