Why won't rivalcfg accept my button mapping command?

November 14, 2026 2 answers
Asked by Jorlet-3v

I'm trying to disable button 4 on a mouse with rivalcfg. The command rivalcfg --buttons(button4=disabled) gives me a Bash syntax error near the opening parenthesis. What should the command look like?

Answers

Keldrin-4v

Bash is interpreting the parentheses before rivalcfg gets the argument. There also needs to be a space after the --buttons option, and the mapping itself needs the buttons prefix.

Try rivalcfg --buttons "buttons(button4=disabled)". The quotes keep the mapping together as one argument and pass the parentheses through to rivalcfg.

almost+well_sorted:

That also explains why quoting just "(button4=disabled)" gets past Bash but can still be rejected as an invalid mapping.

Reply to this answer
2m+spindle_694

Check the buttons example for your exact mouse model too. It shows a mapping with a layout and several button assignments inside buttons(...). If the shorter mapping is rejected, compare it with that full example and the options your installed rivalcfg version supports.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions