-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow XDG Base Directory specification #57
Comments
@nbehrnd figured you may be interested in this due to your comment in #16. I'll probably support |
Thanks for the input. I understand where you're coming from and for any other tool, I might follow your suggestion right away. However, I need to think about that because it also breaks the simple to understand pattern of "the next Some people may even use Furthermore, it would require a less clean "look for the next .filetags file in all parent directories"-algorithm since people might choose to use |
I think that's a valid perspective, and I don't intend to support that specific aspect here based on previous comments on this issue. But what I can't excuse is |
I'll keep it in the back of my head, closing it for now and maybe re-open it in future when I came up with a concept that is transparent to the user. And yes, with playing around with NixOS/Home-Manager and re-thinking my own concept of dotfiles, I do understand dotfile minimalism even more. |
I don't get why this issue was closed. I think that |
As I tried to explain above, the location of the Furthermore, this would break the pattern that any sub-hierarchy has its meta-data files attached as well, even when synchronized across different hosts. One single position in $HOME would break functionality here, sorry. Related to the tagfilter file:
What would you like to see here? How would you do the transition of existing hierarchies of current users when this behavior is changed? Why is the current behavior an issue in practice? |
I believe
${XDG_STATE_HOME}/filetags
is a more preferable default directory for tagtrees compared to~/.filetags_tagfilter
for people who want to avoid dotfile clutter. Albeit debatable, one may also want to move${HOME}/.filetags
inside of an xdg base directory, which could be at the following path:${XDG_CONFIG_HOME}/filetags/vocabulary
. If we continue this example, #16 maps to${XDG_CONFIG_HOME}/filetags/filetags.{toml,yaml,...}
.The text was updated successfully, but these errors were encountered: