Currently, when it comes to changing settings in the configuration file, the user must either use some command that toggles a setting, or they need to edit the configuration file in their editor of choice. This means that there are some commands that aren't needed other than to tweak a setting (and so a keyboard combo is used), and also that the user needs to be comfortable with an editor and be capable of editing a JSON file without messing it up (very high chance they'll be fine given the audience for Gemini, but still...).
Consider building a comprehensive configuration screen/dialog that makes it easy to change any setting. Also consider migrating the modification of some of the settings that use commands into this, and drop the commands (this might make sense as part of a v2.x given the breaking change this will be).
Currently, when it comes to changing settings in the configuration file, the user must either use some command that toggles a setting, or they need to edit the configuration file in their editor of choice. This means that there are some commands that aren't needed other than to tweak a setting (and so a keyboard combo is used), and also that the user needs to be comfortable with an editor and be capable of editing a JSON file without messing it up (very high chance they'll be fine given the audience for Gemini, but still...).
Consider building a comprehensive configuration screen/dialog that makes it easy to change any setting. Also consider migrating the modification of some of the settings that use commands into this, and drop the commands (this might make sense as part of a v2.x given the breaking change this will be).