-
Notifications
You must be signed in to change notification settings - Fork 119
It stands for Tag My Shit Up.
It's somewhere between tiramisu and a sudden and unexpected sneeze.
Either log it in the issue tracker or email the mailing-list [email protected].
You should also look at:
To detect file moves/renames would require a daemon process watching the file system for changes and support from the file system for these events. As some file systems cannot provide these events (e.g. remote file systems) a universal solution cannot be offered. Such a function may be added later for those file systems that do provide file move/modification events but adding support for this to TMSU is not a priority at this time.
The current solution is to periodically use the repair
command which will detect moved/renamed files and also update fingerprints for modified files. (The limitation of this is that files that are both moved/renamed and modified cannot be detected.)
TMSU supports a simple query language consisting of the operators and
, or
and not
. To exclude tags, simply prefix them with not
:
For example, pull out your audio books:
$ tmsu files mp3 and not music
The and
operator is implied if you omit it:
$ tmsu files mp3 not music
Yes. (It was developed on Arch Linux.)
One of TMSU's dependencies, the go bindings for FUSE (http://github.com/hanwen/go-fuse) cannot be compiled on FreeBSD. See https://github.com/hanwen/go-fuse/issues/85 for more information.
It now compiles for Windows but it's a little fiddly to do so. Plus there is no virtual filesystem support just yet.
At this time probably not. Help with creating these would be very much appreciated.
- Arch Linux package is available in the AUR.
- Ubuntu stable and daily PPAs are available for Ubuntu 16.04.1+.
If your shell is Zsh then yes, completion is in the misc
directory of the source tree and binary distributable.
No. Maybe one day, or else integration with popular file/media browsers could be provided.
(2016-09) There has been some effort integrating TMSU as a Nautilus extension.
Prior to v0.7.0, TMSU would create a database at ~/.tmsu/default.db
when you first use it.
Since v0.7.0, TMSU does not create a database automatically and one must be initialised with the init
subcommand. Whenever you run init
, a database file is created at .tmsu/db
under the current working directory and will be used whenever you're at or beneath that path. E.g. if you run init
in your home directory, then you will get a database at $HOME/.tmsu/db
and any files you tag in your home directory will go into this database.
Whenever you run TMSU, it will look for a database at .tmsu/db
under the current working directory. If none can be found, TMSU will look for .tmsu/db
in each parent directory in turn, up to and including the root directory.
If a database is not found in the current or a parent directory, TMSU will then look for the default database created by earlier (<v0.7.0) versions of TMSU at ~/.tmsu/default.db
.
Yes. See [Switching Databases](Switching Databases).
The database is a SQLite3 database and can be read with the regular SQLite tooling.
$ sqlite3 ~/.tmsu/default.db
...
sqlite> .schema
...
sqlite> select * from file;
...
sqlite> .q
The database is a standard Sqlite3 database. There are several tools available that can read the database and which can export the rows as CSV, SQL, &c.
To dump to SQL text, you can use the Sqlite3 tooling:
$ sqlite3 ~/.tmsu/default.db .dump >dump.sql