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

Rebind the "forward" button to LSHIFT #18

Closed
semedilino-073 opened this issue Nov 20, 2024 · 5 comments
Closed

Rebind the "forward" button to LSHIFT #18

semedilino-073 opened this issue Nov 20, 2024 · 5 comments

Comments

@semedilino-073
Copy link

semedilino-073 commented Nov 20, 2024

Hello,
I installed mow on Arch and I was trying to rebind my forward button to the LSHIFT, but I ran into some issues that I don't understand. Maybe I'm wrong and I hope so, it would be better. This is the command I'm using:
mow config bind forward key key-code lshift
But this error popped up:
error: Invalid value "lshift" for '<KEY>': invalid digit found in string
Do you have any solutions?

@korkje
Copy link
Owner

korkje commented Nov 20, 2024

Hi! When using key-code you have to provide a number, looks to me like the code for both left and right shift is 16. You can use a tool like this one to look up key codes.

@semedilino-073
Copy link
Author

Hi, thanks for the immediate answer! I didn't expect that, so I'm sorry for my late response.
I ran:
mow config bind forward key key-code 16
And got:
thread 'main' panicked at src/main.rs:39:52: called ``Result::unwrap()`` on an ``Err value: HidApiError { message: "hid_error is not implemented yet" } note: run with ``RUST_BACKTRACE=1`` environment variable to display a backtrace

@semedilino-073
Copy link
Author

Ehmm, I misclicked :/

@korkje
Copy link
Owner

korkje commented Nov 23, 2024

That's probably the hidapi failing, you can try running as root (with sudo) or create a "rules" file as described here.

@semedilino-073
Copy link
Author

semedilino-073 commented Nov 23, 2024

YOU'RE A GENIUS!! Sorry for that, but seriously, thanks! The solution was to just run the command as sudo. Thanks again!

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

2 participants