tx0

4 ms·

1.
by tx0 15y ago
It does not work exactly this way. When you create a file "DSCN0001.JPG", it receive a prefix, even if it's not conflicting, becoming, lets say, "123_DSCN0001.JPG". But both you and your software (say: a filemanager) are presuming the file
2.
by tx0 15y ago
Tagsistant 0.4 doesn't use AND any longer, but that brought the need for a termination operator, which is '=' so far, but probably will be changed for shell comfort. The 0.2 query mpoint/rock/AND/seattle/ becomes mpoint/tags/rock/seattle/=/
3.
by tx0 15y ago
Did you use an ontology or some kind of "manifest" to bootstrap hierarchical relations between tags? I'm thinking about splitting Tagsistant into a client and a server to provide a multiuser environment, and probably some ontological founda
4.
by tx0 15y ago
I always thought at Tagsistant as an archiving tool, but you are totally right. But files are also accessible from the archive/ directory where nothing is supposed to change as a consequence of tagging. Can be a reasonable compromise?
5.
by tx0 15y ago
Tagsistant is not supposed to replace posix filesystems and can't be used in system directories like /bin or /etc. Tagsistant is a personal tool to organize files (and directories, starting with version 0.4). It provides a plugin architectu
6.
by tx0 15y ago
Tagsistant 0.2 does not allow to store two files with the same name, exactly as you say. But Tagsistant 0.4 will! Well, at the little compromise of having a small unique number prepended to each filename. Tagsistant 0.4 has a broader vision