Andrea Novara

How would you then set them apart from real files? I mean, when you scan your repo with a tool, like a `find store/t1/t2/@/ -exec ...` or a `cp -r...

Normal use of Tagsistant is storing files inside a repository for later retrieval and editing in place. Migration between repositories is a nice to have plus, but the very first...

Hi, where did you got the information that running as root is the recommended setup? The recommended setup is the exact opposite, but FUSE must be first configured to allow...

If I don't get this wrong, part of what you envision is already possible. Please mount Tagsistant with `-o allow_other`, then try to copy some content inside Tagsistant and later...

The +/ operator forces Tagsistant to list all the tags endlessly. I don't see a way to prevent an indexer or a file manager from scanning them again and again....

A limit on the tags shown in `store/` is a limit for everyone: for the indexer you would like to not iterate endlessly, but also for the user composing its...

I see, seems like I've misunderstood @conrad-heimbold proposal. Thanks @ivan-kolmychek. Limiting the depth of the search instead of the width of the returned results is definitely better. However it does...

I see why this would be useful. However, the introduction of the `&/` operator would require a change in the query parser. A similar effect could be obtained using a...

Tagsistant has a pluggable architecture for autotagging. A regular expression plugin is already available as `src/plugins/tp_filename_rx.c`. It contains an extensive documentation as a comment. Otherwise, writing a custom, dedicated plugin...

Seems like you're mixing two topics into one issue only. The proposal of a sync procedure to exchange information between two Tagsistant repositories is an interesting point. I think that...