expand relative path ~/.config/vikunja to $HOME/.config/vikunja **WINDOWS** #147
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "funkythings/api:windows-env-compat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Same as #146, but compatible with windows paths. Not sure actually HOW the backend runs on windows with paths like
/etc/vikunja
etc...Just in caseWIP: expand relative path ~/.config/vikunja to $HOME/.config/vikunjato WIP: expand relative path ~/.config/vikunja to $HOME **WINDOWS**/.config/vikunjaWIP: expand relative path ~/.config/vikunja to $HOME **WINDOWS**/.config/vikunjato WIP: expand relative path ~/.config/vikunja to $HOME/.config/vikunja **WINDOWS**Please run
go mod tidy
,go mod vendor
and commit the result.WIP: expand relative path ~/.config/vikunja to $HOME/.config/vikunja **WINDOWS**to expand relative path ~/.config/vikunja to $HOME/.config/vikunja **WINDOWS**@funkythings Please resolve conflicts (I think these came through merging #146)
I'm confused, did you merge #146 with master first? And now want to merge #147?
#146 is merged yes. It seems like I did not pay attention at the similarities of these two PRs. Sorry for that.
I would prefer if this one could get merged, since as you already stated it has better compatibility with Windows etc - even if it basically overrides the changes made in #146.
Ok, sry for the delay. I had to send my laptop in for repair. Will take a look as soon as possible
Should do it
I can push a tiny change to make more clear, which of the many possible config file locations where actually used. Are you interested in that? Helped me out in debugging an issue in a
yml
file a lot. I can imagine this information is useful for people, in case they run into similar issues.Adding extra bit of information sounds like aa great idea, please go ahead!
Added the bit of information, plus formatted. Vim messed it up
I also fixed the default yaml config file with a single pair of "" at the right spot.
Looks good, thanks.