Two different config directory in my homedir on Linux #39
Comments
|
Thanks for the report! We'll look into it :) |
|
I actually wasn't aware of the fact that kivy was creating its own config file at all, but this came-up again as I was working on adding a "settings" screen to the GUI in #14, which depends on #16. Interestingly, I discovered that kivy has a built-in module named Settings that we can use: It simply uses kivy's Config module, which itself extends Python's ConfigParser. This is a very powerful and robust design. If we use it for implementing the BusKill config file, then we might be able to combine both into the same file. |
|
Here's what the existing file looks like on my dev system This is actually really cool, as it looks like the user can tweak stuff in the GUI app directly, like font size. That may help provide a workaround for strange bugs like #37 |
|
In addition to above, to solve this issue, I'd have to move the whole |
maltfield
added a commit
that referenced
this issue
Nov 13, 2022
…rser object and the App's build_config() method * #16 TODO: update the `setupDatDir()` to prioritize $XDG_CONFIG_HOME on linux systems * https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html#variables * #39
maltfield
added a commit
that referenced
this issue
Nov 13, 2022
* on linux, we prioritize trying to use the XDG data dir to contain our buskill DATA_DIR by first trying to use dirs defined in the XDG_DATA_HOME env var (with final fallback on $HOME/.local/share) * this commit also adds logic to place the kivy config.ini in the buskill DATA_DIR and creates a buskill section in that config.ini file. * #39 TODO: make sure it doesn't create the '.kivy/config.ini' before build_config() is called (so it just makes an copy as is not desired). If it does, see if you can pre-empt its creation (or at least clean it up after) TODO: see if you can make the [buskill] section appear above all the other [kivy] sections
Closed
|
I downloaded the latest version of the app today to see if this ticket is complete. Before I executed the BusKill app, I confirmed that my fresh new DispVM had no directories named After opened & closed the app, I found that all the kivy-related dirs & files were located inside the same |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I see two different directories being used for the buskill app on my machine using two different names:
~/.buskill(just for the cache)~/.kivy(everything else)Expected behavior
I would expect to see the same name for that app. I didn't know what "kivy" was, "buskill" on the other hand is exactly what I was expecting to see.
Additionally, I would suggest using the standard locations:
$XDG_CACHE_HOME/buskill, falling back to$HOME/.cache/buskill$XDG_CONFIG_HOME/buskill, falling back to$HOME/.config/buskillVersions (please complete the following information):
The text was updated successfully, but these errors were encountered: