Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error message "Keyboard shortcut conflicts with existing shortcut" #68

Open
andreoliwa opened this issue Oct 18, 2023 · 4 comments
Open

Comments

@andreoliwa
Copy link
Contributor

2023-10-18_11-50

Steps to reproduce:

  1. Go to the plugins page and disable logseq-automatic-linker
  2. Enable it again.
  3. The error messages show up.
@stucash
Copy link

stucash commented Oct 25, 2023

I have exactly the same issue upon update for the plugin; by re-enabling the plugin as described above reproduced the error as well. I am on 1.5.5, which seems to be the latest version.

@AndreasSlette
Copy link

I just installed this plugin and got the same error message. I solved it by changing the shortcut keybinding from "mod+p" to "mod+alt+p". You can change the keybinding by going to plugins and selecting "open settings".
image

@andreoliwa
Copy link
Contributor Author

The error disappeared after I upgraded Logseq to 0.10.3.

But auto-parse links also stopped working, so maybe something changed upstream.

@BradKML
Copy link

BradKML commented Jan 26, 2024

This also applies to Windows for "Ctrl+P" which conflicts with "Move cursor up / Select up" so there needs to be a way out of this
@AndreasSlette maybe I will follow suit with "Ctrl+Alt+P" as well? I have LogSeq up to date

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants