Search first

• I searched and no similar issues were found

What Happened?

Hi,

Default key-bindings of different addons/built-in key-bindings conflicts (being same) every time after Logseq updates or individual plugin updates or enable/re-enabled plugins. Even if I change or disable/remove the key-bindings and resolve the issue, the relapse to conflicting scenario after updates/re-configurations.
The one with attached image, occurs the most on regular basis. it's plain-old annoying.
Similar issues occurs with other plugins as well that comes with key-binding and then conflicts with my custom (user configured) key-bindings or other plugin/module's key-bindings.

More annoyingly they just keeps stuck and stacked (often, repetitively and multiple balloon notifications) on the screen until manually closed. overlaps and causes invasive disruption in working area and clogs working space (wastes screen real-estate)

Reproduce the Bug

1. Get both feature/modules/plugin installed and active
2. Change / delete either or both key-binding
   3.a Wait for next update ( of logseq or of module/plugin ) ;
   3.b. Alternatively, Disable conflicting plugin(s) > { 3.b.1 optionally: close app > open app } > Then re-enable might trigger conflict as well in case of native key-binding conflicts. conflict with user configured key-bindings may not always be recreated this way.
3. The issue "should" reoccur. ( just to be clear, it's not always straight-forward action-steps that re-produce the issue, but at some point it does. )

Expected Behavior

Changed/modified/deactivated ( no/null key-binding) should not be reverted upon updates.
Upon installation or activation (enabling), new/updated plugins-key-bindings that conflicts with existing built-in or other plugins user-modified key-bindings should ask permission to overwrite, deactivate ( their own key-binding ), snooze/resolve-later ( temporarily deactivate latest key-assignment until next session or for a certain snooze period )

Screenshots

Desktop or Mobile Platform Information

App Version: 0.10.14
Git Revision: dde0aba
Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.10.14 Chrome/132.0.6834.210 Electron/34.5.6 Safari/537.36
Language: en-US
Plugins: logseq-summarizer (0.0.4), logseq-wrap (v0.10.3), logseq-paste-more (v1.5.9), logseq-block-calendar (v0.2.11), logseq-raindrop (v0.5.1), logseq-awesome-ui (v2.4.0), logseq-plugin-automatic-url-title (v1.1.0), logseq-move-block (v1.0.0), logseq-link-unlinked (v1.5.1), logseq-calendars-plugin (2.2.2), logseq-excalidraw (v1.5.1), logseq-todo-plugin (v1.22.0), logseq-journals-calendar (v0.11.0), logseq-awesome-styler (v3.7.1), logseq-copy-code-plugin (v.1.2.0), logseq-marks (v0.0.3), logseq-bionic-speedreader (1.0.1), logseq-heatmap (v2.4.3), logseq-bullet-threading (v1.1.4), logseq-flow-nord-theme (v0.10.39), logseq-matrix-amoled-theme (1.1.0), logseq-random-note (1.1.2), logseq-todoist-plugin (v6.0.2), logseq-lock (v0.0.7), logseq-vim-shortcuts (v0.1.22), logseq-ol (v0.6.1), logseq-awesome-links (v1.15.16), logseq-todo-master (v1.10.3), logseq-plugin-gpt3-openai (v1.13.2), logseq-tabs (v1.19.4), logseq-helium-plugin (v.2.1.3), logseq-block-to-page (v1.3.0), logseq-agenda (v3.13.1), logseq-long-form (v1.6.2), logseq-focus-mode (v1.0.4), logseq-pomodoro-timer (1.0.3), logseq-automatic-linker (1.7.0), logseq-metrics (0.22), logseq-kanban-plugin (v3.8.1), logseq-file-manager (v1.4.0), logseq-tags (v0.1.2), logseq-interstitial (0.1.7), logseq-git (v1.7.0), logseq-task-management-shortcuts (v0.0.3), logseq-habit-tracker (v0.4.4), logseq-graph-analysis (0.12.0), logseq-sidebar-preset (v1.0.1), logseq-mark-map (v0.4.6)

Additional Context

There should/can be multiple key-bindings presets that can be toggled/changed on off as per user's marginal preference.
Each plugins that comes with their own key-bindings should/can ha single toggle switch to enable/disable key-bindings.
If conflict arises during toggling on, then those particular key-bindings can be shown (along with it's conflicting plugins name in pairs) and user can choose activate, disable, or change either one or both, at that time, key individual bindings should be in application, or whether to toggle off only that particular key-bindings instead of all that the plugin put in effect.

Extended Idea: In case of Snooze/unresolved conflicting cases, if user press a certain key-combination that causes the conflict may give an option dialog to user asking which module/plugin's task the user wants to trigger along with a "resolve now" option that leads to a view where providing key-binding input fields for both module/plugin side-by-side key-bindings. User may set/change/disable either one, or both, and/or leave one or all blank/unset (such that resolving and setting key-binding at the given point of time doesn't become mandatory/obligatory that may break users workflow, thought-flow.

PS: Sorry for my highly complex sentences produced in the flow of my highly convoluted thought process and patterns. I wish natural language were more like programming languages like python or even xml so that object adherence could be put in unanimously singularized yet extensible. 😖. . . aanndd . . . MORE SORRY for the last PS paragraph with abundance of inconspicuous medieval words!

Thanks

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)