Add config path for windows OS

[morrieinmaas]

Signed-off-by: morrieinmaas [email protected]

closes #54

[morrieinmaas]

It's WIP @blu3beri . Need to test that first. Windows VM being a right b*** atm.

[berendsliedrecht]

Approved when tested.

[morrieinmaas]

@blu3beri Just a little update:
The good news:

• works on WSL

The bad news:
This doesn't quite work yet for windows powershell/native. There are several problems:

• When compiling the switch checking for cfg!(windows) works but the compiler isn't happy with HOME not being defined (even though that is just for unix). Maybe we need to add sth like compile target or sth as a switch?
• %AppData% just creates a new folder of that name in the project root -> compiles but config not found then
• Also found that apparnelty %USERDATA% is a place for config files / the equivalent of unix $HOME -> results in the same behaviour as the previous error.

I'll continue to figure this out (now that I have a WIndows machine up and running). Just have no clue how Windows works so need to do some digging.

On another note, I needed to install some dependencies like C++ compiler/build env for windows for this to compile in the first place. Maybe we can open a ticket about this. I'm just not sure how to articulate this properly (yet) as again I don't know how windows works and how to define dependencies for a rust project for windows compile or whether to just set that in the README and let people know and then that's enough.🤷‍♂️😅

[berendsliedrecht]

Okay, yeah the %...% was a small chance that it would work. It is the same as how "~" works in unix, in the sense that it expands to another full path, like /users/foo

On the compiling step, it is not really a problem. People who want to contribute to a rust project must deal with them themselves, like with any language. And the binary comes, 99.999% sure, with all the bells and whistles to work.

I do think the error about home not being specified is odd. Could you send a screenshot of that?

[morrieinmaas]

@blu3beri let me know if you have any more feedback. This works now for windows (and doesn't break unix.

One thing I see is we can probably extract the logic for path creation to the config file inot a function as it's the same code in 2 places now. Can do that here or in another PR. (or not at all if you don't see fit)

[morrieinmaas]

Alright @blu3beri