Keymap editor shows wrong shortcuts (maj instead of ctrl)

[hippalectryon-0]

Search first

• [X] I searched and no similar issues were found

What Happened?

I was trying out the zoom feature. I read on the wiki that on Windows zooming in is with "Ctrl" + "+", which indeed works.

However, on the keymap page, it's shown as "Maj" + "+", which doesn't do anything.

The other zoom controls also share this same issue.

I haven't checked whether this is specific to zoom commands but it's probably not.

Reproduce the Bug

Open keymap and look at the default "Zoom in" shortcut: it displays "shift +" instead of "control +"

Expected Behavior

No response

Screenshots

PS: I'm on AZERTY

Desktop or Mobile Platform Information

Windows 10, Desktop app 0.9.19

Additional Context

No response

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

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

[github-actions[bot]]

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, 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!

[hippalectryon-0]

This issue is still relevant in 0.10.8