[PSA] You probably want equal instead of + (plus/bracketright)

[lb-pendula]

I'm posting this as I was at first utterly baffled when trying to make a hotkey combo of meta and plus, and the docs did not lead me in the right direction. It was only when I put some logging inside the lib itself that I realised I really wanted the equal key and that my desired hotkey could be described as meta+equal (complementing my meta+minus key that worked fine).

I suspect this is a common mistake that devs who don't normally work with a lot of hotkeys (such as myself) forget that keys should usually be nominated by their standard function and not their modified function.

If the docs could be updated in a way that highlights this pitfall I think it would save a lot of issues being filed for hotkeys that don't work :)

[JohannesKlauss]

This is a layout specific problem that gets addressed in version 5.

This has been fixed in pre release 5.0.0-1. Please try out this version.
To listen to = use you just use useHotkeys('=', callback, {useKey: true})

Please let me know if that fixes your issue.

[msharkeyiii]

I want to jump in here and call out in addition my issue earlier with minus - ticket I closed previously. Today I also had troubles with a forward slash / as part of a shortcut was only bugging out on a Chromebook, but worked fine on a Mac. Mind numbing trying to debug it, but found that using the words fixed it.

Documenting for posterity and the search engines:

Use this, not that:
slash instead of /
minus instead of -
equal instead of =

[oleksandr-danylchenko]

Thanks, @msharkeyiii! The plain - wasn't recognized on Mac, but the minus worked immediately!