Skip to content
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

Keeping track of all tags for a global search #29

Closed
lmburns opened this issue Jun 13, 2021 · 1 comment · Fixed by #30
Closed

Keeping track of all tags for a global search #29

lmburns opened this issue Jun 13, 2021 · 1 comment · Fixed by #30

Comments

@lmburns
Copy link
Contributor

lmburns commented Jun 13, 2021

Feature Request

I'm on macOS and I also use this program which is another tagging tool. It has quite a few features and I understand that your version is compatible with more than just macOS, so not all features would necessarily be compatible; however, here is my request:

Add support to somehow keep track of all the tags that are set. For instance a file could be placed in ${XDG_DATA_HOME:-$HOME/.local/share}/wutag that could be some sort of database, or just some plain text file that would allow for the user to list all their tagged files. Perhaps the option to sort by tag and or directory as well (in this global feature). This feature is similar to the --home or --local option in the program I linked above.

Edit:
I might also add that it would help to have this feature because when using the closes thing to it (wutag -d ~ list '**'), I get several errors on some files. For example:

ERROR error: Permission denied (os error 13)
ERROR provided file doesn't exists

It would be helpful if I could clear these with clear or know which files these are referring to.

@vv9k
Copy link
Owner

vv9k commented Jul 25, 2021

I thought about storing some sort of state briefly so I opened #6 and indeed this would greatly increase user experience. storing the state in OSs cache dir might be better, I would prefer to keep out of users home directory.

I will also put some work into the error messages. It should at least state what file the error refers to.

@vv9k vv9k mentioned this issue Jul 28, 2021
@vv9k vv9k closed this as completed in #30 Aug 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants