Use "$HOME/.config/filetags" for overriding default options
novoid opened this issue · 3 comments
If I want to override, e.g., the default tagtrees folder depth value, I want to use a user-related config file.
This idea might be better "solved" via #17 because moving it to .filetags files allows for having different defaults for different sub-hierarchies of my file system.
Later joining this party, I start to think the deposit of file .filetags containing the controlled vocabulary within the Linux' path ~/.config/filetags/ would be an advantage. Because the directory ~./config with configurations of many programs already is of special interest during a backup, this would offer storage in a place safer than just «in home», a level higher.
An observation (in Linux Debian 12) perhaps interesting to share: it is possible to use # in file .filetags to insert comments/temporarily mute individual entries. It equally is possible to organize entries in groups, separated by a single empty line, too.
I do think that moving .filetags to somewhere else would break the pattern of "filtags is looking for the next .filetags up in the hierarchy".
However, the entries in .config/filetags would not contain tags. This file would contain different defaults. So I don't think that mixing "using other defaults" and "defining a set of tags for a certain sub-hierarchy" should be mixed.
And yes, comment lines have been implemented long time ago. The order of lines in the file is not relevant. The only thing that matters is if there are multiple tags in the same line (mutual exclusive tags) or not. I do use comments for my tags very often.