Change it so $ gamepad-launcher.sh launch --manual must be specified to edit the override file manually, rather than just $ gamepad-launcher.sh launch (which will now print the usage statement instead).
$ gamepad-launcher.sh --manual will run systemctl --user edit gamepad-launcher.service; $ gamepad-launcher.sh --manual <filename> will open for edit the file in the same folder as the script's automatically-generated .conf files.
Add "built-in" in the form of $ gamepad-launcher.sh launch --built-in [name] . Remove the "suggestions" action; running $ gamepad-launcher.sh launch --built-in without another argument will print the list of available built-ins.
(Do of the above for cleanup actions too)
Improve readability of the usage statement.
Consider adding a symlink at install time from $BIN_DIR/gamepad-launcher to gamepad-launcher.sh.
Document all changes within the code and in the README.
Change it so
$ gamepad-launcher.sh launch --manualmust be specified to edit the override file manually, rather than just$ gamepad-launcher.sh launch(which will now print the usage statement instead).$ gamepad-launcher.sh --manualwill runsystemctl --user edit gamepad-launcher.service;$ gamepad-launcher.sh --manual <filename>will open for edit the file in the same folder as the script's automatically-generated .conf files.Add "built-in" in the form of
$ gamepad-launcher.sh launch --built-in [name]. Remove the "suggestions" action; running$ gamepad-launcher.sh launch --built-inwithout another argument will print the list of available built-ins.(Do of the above for cleanup actions too)
Improve readability of the usage statement.
Consider adding a symlink at install time from $BIN_DIR/gamepad-launcher to gamepad-launcher.sh.
Document all changes within the code and in the README.