umu-commander 1.5.1__tar.gz → 1.5.2__tar.gz

{umu_commander-1.5.1 → umu_commander-1.5.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: umu-commander
-Version: 1.5.1
+Version: 1.5.2
 Summary: umu-commander is an interactive CLI tool to help you manage umu.
 Project-URL: Homepage, https://github.com/Mpaxlamitsounas/umu-commander
 Project-URL: Issues, https://github.com/Mpaxlamitsounas/umu-commander/issues
@@ -21,7 +21,15 @@ What directories each Proton version is being used by is tracked within `trackin
 
 Vanilla umu configuration files currently do not support setting environmental variables, this tool adds such functionality by adding an extra TOML table in the umu config itself. An example config is available under the name `example_config.toml`.
 
-umu-commander will look for your installed Proton versions using a predetermined list of directories, if you notice some versions missing, the listed can be edited within the `configuration.py` file in the src directory.
+### Config
+The configuration file lives at `~/.config/umu-commander.toml`. Within it, you can edit the following:
+* PROTON_PATHS: List of directories umu-commander will search for Proton versions.
+* UMU_PROTON_PATH: Directory where umu itself downloads its umu Proton versions.
+* DB_NAME: Tracking DB filename.
+* DB_DIR: Directory where the Tracking DB is stored.
+* UMU_CONFIG_NAME: Name of the umu config created using umu-commander run.
+* DEFAULT_PREFIX_DIR: Directory where WINE prefixes are scanned.
+* [DLL_OVERRIDES_OPTIONS]: Category to list possible DLL overrides in "Label" = "Override string" format.
 
 ### Verbs
 umu-commander needs one of the following verbs specified after the executable name:

{umu_commander-1.5.1 → umu_commander-1.5.2}/README.md

@@ -6,7 +6,15 @@ What directories each Proton version is being used by is tracked within `trackin
 
 Vanilla umu configuration files currently do not support setting environmental variables, this tool adds such functionality by adding an extra TOML table in the umu config itself. An example config is available under the name `example_config.toml`.
 
-umu-commander will look for your installed Proton versions using a predetermined list of directories, if you notice some versions missing, the listed can be edited within the `configuration.py` file in the src directory.
+### Config
+The configuration file lives at `~/.config/umu-commander.toml`. Within it, you can edit the following:
+* PROTON_PATHS: List of directories umu-commander will search for Proton versions.
+* UMU_PROTON_PATH: Directory where umu itself downloads its umu Proton versions.
+* DB_NAME: Tracking DB filename.
+* DB_DIR: Directory where the Tracking DB is stored.
+* UMU_CONFIG_NAME: Name of the umu config created using umu-commander run.
+* DEFAULT_PREFIX_DIR: Directory where WINE prefixes are scanned.
+* [DLL_OVERRIDES_OPTIONS]: Category to list possible DLL overrides in "Label" = "Override string" format.
 
 ### Verbs
 umu-commander needs one of the following verbs specified after the executable name:

{umu_commander-1.5.1 → umu_commander-1.5.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "umu-commander"
-version = "1.5.1"
+version = "1.5.2"
 authors = [
   { name="Mpaxlamitsounas", email="worldstudy123@gmail.com" },
 ]

{umu_commander-1.5.1 → umu_commander-1.5.2}/src/umu_commander/main.py

@@ -59,6 +59,7 @@ def main() -> ExitCode:
 
     tracking.untrack_unlinked()
     db.dump()
+    config.dump()
 
     return ExitCode.SUCCESS