keyboard shortcut conflicts with... itself?

[Oaklight]

What happened?

I got a conflict notification when I installed "tidy-blocks." Then I changed the shortcut from default mod+ctrl+x to alt+ctrl+x but ended up with another conflict. This one is a bit confusing to me: why does it conflict with itself?

Reproduce the Bug

1. go to settings of 'tidy-block`
2. change keyboard shortcut to toggle block properties

Expected Behavior

shortcut should only conflict with existing shortcuts to other functions

Screenshots

Desktop Platform Information

Deepin 20.7
Logseq v0.8.7

Mobile Platform Information

No response

Additional Context

No response

[menelic]

Just had a similar error message with a different plugin - the great Citation Manager plugin - when updating from its v2.0.2. to 2.0.3. and without having changed the default keyboard shortcuts:

[hiway]

+1

I am writing a plugin.

import '@logseq/libs'
import ElizaNode from 'elizanode'


async function main() {
  var eliza = new ElizaNode()

  logseq.App.registerCommandShortcut({
    binding: "ctrl+shift+enter",
    mode: "global"
  }
    , async () => {
      const current_block = await logseq.Editor.getCurrentBlock()
      const input = await logseq.Editor.getEditingBlockContent()
      if (!input) {
        console.log("Eliza: No input, skipping...")
        return
      }
      const output = eliza.transform(input)
      const formatted_output = `Eliza: *${output}*`

      const reply_block = await logseq.Editor.insertBlock(current_block!.uuid, formatted_output, { sibling: true })
      await logseq.Editor.insertBlock(reply_block!.uuid, "", { sibling: true })
    })
  console.log('Eliza: ready.')
}

logseq.ready(main).catch(console.error)

I get this error every time I reload:

In order to reload the plugin, I have to quit Logseq and start the app again.

[xxchan]

In order to reload the plugin, I have to quit Logseq and start the app again.

A workaround for plugin development is to reload Logseq.. 🥲

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!

[xxchan]

not fixed

…

On Fri, Jun 23, 2023 at 2:02 AM github-actions[bot] < ***@***.***> wrote: Hi There! 👋 We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website <https://logseq.com>. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help! If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment. Access additional Logseq <https://logseq.com> 🚀 resources: - *Forum*: https://discuss.logseq.com - *Blog*: https://blog.logseq.com - *Docs*: https://docs.logseq.com Thanks for your contributions to Logseq! If you have any other *issues* <https://github.com/logseq/logseq/issues/new/choose> or *feature requests* <https://discuss.logseq.com/c/feature-requests/>, please don't hesitate to let us know <https://github.com/logseq/logseq/issues/new/choose>. We always welcome pull requests too! — Reply to this email directly, view it on GitHub <#6838 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJBQZNMJ6QCXSGCPZF5H4JTXMTMKDANCNFSM6AAAAAAQX3AAOM> . You are receiving this because you commented.Message ID: ***@***.***>

[redactedscribe]

I have several plugins and I often see errors about shortcuts conflicting with themselves, e.g.: :plugin.logseq-bionic-speedreader/$shortcut$mod_b_mod_s ctrl+b ctrl+s Keyboard shortcut conflicts with existing shortcut: plugin.logseq-bionic-speedreader/$shortcut$mod_b_mod_s. It has been happening for a long time now, without having changed any default shortcuts.