• Feature information

The minimum I would love to see supported is allowing the user to provide userSettings.json and userConfigurations.json files and having that just work. Beyond that, easing this workflow by bolstering the CLI with options to add, edit, and remove parsers and other settings, building off presets too or existing configurations, would be legendary.

• Additional context

I have attempted to do this, and noted the following:

1. Providing my own userSettings.json under .config/steam-rom-manager/userData before running the program initially does appear to work correctly already!
2. When I provide a valid userConfigurations.json file and boot up the GUI to see if it loads it correctly, it overwrites the configuration of userAccounts.specifiedAccounts and steamCategories to be []. When you change them in the interface and save, I don't see any errors on the command line or in the interface, but essentially it acts as if it doesn't save your changes. I'm having a hard time tracking down how and where this fails ultimately.
3. This mostly only seems useful to me if the CLI can also be run without a graphical desktop session. In the end I want to be able to configure steam-rom-manager and add every game it matches to steam in a non-interactive terminal which can be run from a remote machine. It is currently impossible to run commands like steam-rom-manager list/add this way. I have attempted to prefix these commands with a virtual display manager in headless mode like xvfb-run, but still no luck yet (new territory for me).