Hi, list.
Wrote this tmsu wrapper tool about a month ago to scan directories,
finding repositories and filename/shebang patterns and tag the files
accordingly:
https://github.com/mk-fg/codetag
Idea is to then use tmsu directly like "tmsu files lang:py" to find all
python sources in one's "dev area".
Other currently supported tags are, as mentioned, repository scm tags
(e.g. "scm:git" or "scm:hg") and code hosting (parsed from scm
configs), e.g. "host:github" or "host:whatever-you-configured".
Includes simple rsync-like (but with re2 patterns instead of globs)
path filters to skip descending into or tagging known "tmp" areas or
caches.
All features are configurable via yaml config:
https://github.com/mk-fg/codetag/blob/master/codetag.yaml.dist
And the whole thing is written in Go, same as tmsu.
I wrote a bit longer announcement in the blog post here:
http://blog.fraggod.net/2013/02/04/codetag-tmsu-tag-all-the-things-and-go.html
At first, I wanted to use tmsu as a lib there, but given that it's
current version will be statically compiled into the tool and CLI tmsu
tool might diverge from it, decided to just use CLI interface (call
tmsu tool as a subprocess) instead.
Performance-wise, the difference is probably negligible anyway.
Thought it might be useful to create a bit more noise on the list, if
only to draw attention to such interesting tmsu use-cases.
Should've probably done it about a month ago, but oh well.
Huge thanks to Paul for the most awesome tool, which led me to this idea
in the first place.
--
Mike Kazantsev //
fraggod.net