Post History
No wonder it's hard to find good programs - it's no longer necessary! At some point this became a built in part of Xorg via xinput. The process is something like this: xinput list and find the ...
Answer
#2: Post edited
- No wonder it's hard to find good programs - it's no longer necessary! At some point this became a built in [part of Xorg via xinput](https://wiki.archlinux.org/title/Libinput#Via_xinput_on_Xorg).
- The process is something like this:
- * `xinput list` and find the ID of your mouse
- * `xinput get-button-map $MOUSE_ID` and see the current map
- * `xev -event button | grep button` to check which button is which
- * `xinput set-button-map $MOUSE_ID $NEW_BUTTON_MAP` to remap
- To make it permanent you can create Xorg config files (described in the link).
- No wonder it's hard to find good programs - it's no longer necessary! At some point this became a built in [part of Xorg via xinput](https://wiki.archlinux.org/title/Libinput#Via_xinput_on_Xorg).
- The process is something like this:
- * `xinput list` and find the ID of your mouse
- * `xinput get-button-map $MOUSE_ID` and see the current map
- * `xev -event button | grep button` to check which button is which
- * `xinput set-button-map $MOUSE_ID $NEW_BUTTON_MAP` to remap
- This will only work until the next reboot.
- To make it permanent you can create Xorg config files (described in the link).
#1: Initial revision
No wonder it's hard to find good programs - it's no longer necessary! At some point this became a built in [part of Xorg via xinput](https://wiki.archlinux.org/title/Libinput#Via_xinput_on_Xorg). The process is something like this: * `xinput list` and find the ID of your mouse * `xinput get-button-map $MOUSE_ID` and see the current map * `xev -event button | grep button` to check which button is which * `xinput set-button-map $MOUSE_ID $NEW_BUTTON_MAP` to remap To make it permanent you can create Xorg config files (described in the link).