You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For programs which place files inside of the user directories, such as logs and tempfiles, the program may place files in the dotfiles store, rather than next to the files that are linked.
Being able to generate the empty directory structure if it doesn't exist would be very useful. Especially when installing dotfiles in the following situations:
Program does not generate configuration directory automatically
Program has not been installed yet
Program has not been run yet
I specifically had this issue with glzr-io/glazewm and glzr-io/zebar on Windows when attempting to install my dotfiles on a system without either program having run for the first time. The files use this structure:
Before running tuckr set *, the .glzr directory does not exist inside of %USERPROFILE% my dotfiles look like this:
And any log files generated by zebar or glazewm are now placed in their respective directories inside of the dotfiles store.
My current workaround is going to be creating a pre hook for both which generate the necessary destination directory structure, but to me it feels like this should be default behavior, or at the very least a flag that can be passed to tuckr.
The text was updated successfully, but these errors were encountered:
Yes, you're correct. #43 started to fix this exact issue. When multiple hooks share an uncreated directory one of them will link it with no regard for the other ones so you'll just end up with one group swallowing the others. So I started writing a file tree so I can detect and prevent these issues. I've just been slow to implement it because I'd been distracted with other things and very very slowly chipping away at this problem.
For programs which place files inside of the user directories, such as logs and tempfiles, the program may place files in the dotfiles store, rather than next to the files that are linked.
Being able to generate the empty directory structure if it doesn't exist would be very useful. Especially when installing dotfiles in the following situations:
I specifically had this issue with glzr-io/glazewm and glzr-io/zebar on Windows when attempting to install my dotfiles on a system without either program having run for the first time. The files use this structure:
Before running
tuckr set *
, the .glzr directory does not exist inside of %USERPROFILE% my dotfiles look like this:After running
tuckr set *
, the %USERPROFILE% directory looks like this:And the dotfiles directory has become polluted as follows:
And any log files generated by zebar or glazewm are now placed in their respective directories inside of the dotfiles store.
My current workaround is going to be creating a pre hook for both which generate the necessary destination directory structure, but to me it feels like this should be default behavior, or at the very least a flag that can be passed to tuckr.
The text was updated successfully, but these errors were encountered: