[BUG] Sample config not working #203
Comments
|
I tried a minimal config instead and still no joy. I believe there might be an issue with
Tried installing via the AUR instead but that fails straight away due to |
|
Hi @silentjay, I guess pipx is a no-go since dooit-extras is a library and not an actual binary that can run Even pipx includes this warning:
That is weird, I just tried with yay and it worked? Can you share some logs? My Logs |
|
Thanks, had to do an system update then run yay, think my mirrors were out of date. Still can't get a minimal config working e.g. ~/.config/dooit/config.py |
Wdym by |
|
There are no changes to dooit when ran, it uses the default config. Can't help but think i'm missing a step somewhere? |
|
Very weird, although the snippet you shared looks very similar to the defaults so you did not notice? idk. Can you maybe try a sample config from here That way you'll know for sure if things aren't working? |
|
I've tried all 3 sample configs, and the minimal config I posted earlier just had one change in the Fixed it! There was a |
|
Woah wth. I'll have to add this in the docs. Glad it worked out ! |
|
Did we solve your problem? Consider sponsoring my work through github sponsors 😄 |
|
Need to test it a little more but looks like I have to nuke |
|
You can also set this environment variable: |
|
Thanks, I'll have a think about that as it'll effect all my system wide python scripts. Turns out every time you close down dooit, if you don't wipe the pycache before reopening it reverts to the default config, regardless if you make changes to it or not. The actual config files contents remains the same though. |
|
That is very weird. I'll take a look into it today. You're using Arch right? |
|
Yup on Arch. I tried swapping in the different sample configs, same issue. If I delete pycache then the config loads successful. If I then close dooit and run again, the new config is shown briefly, maybe a second or two, then it reverts back to the default config. Subsequent reloads of dooit will never show the new config, even briefly. Very strange behavior. |
|
This happens for me too on fedora KDE and it was driving me crazy. Is there no build-in way to reload the config without having to figure out that you need to manually remove the pycache folder in the config-loc? |
|
Hi @ingur and @silentjay. Unfortunately I can't replicate the behaviour on my machine. However I had some doubts so I tweaked a few things in the develop branch, can you install it via pip (in a virtual environment) and check if the behaviour is replicated? In the virtual env, you can do Lemme know if this fixes it |
Using dooit v3.0.2 and dooit-extras v0.1.0
Copied the Catpuccin sample config into my config file
~/.config/dooit/config.py. However no changes are observed in dooit. Am I missing a step?The text was updated successfully, but these errors were encountered: