`tmsu mv` command for moving files while retaining tags about tmsu

[oniony]

OK, after looking at issue #20, I've decided I'll include a set of shell functions with TMSU. Currently I have:

• tmsu-rm
• tmsu-mv
• tmsu-mergefiles

This should allow users to do these operations simply without TMSU itself performing any changes to the managed files on disk.

I've created a new issue #35 for this.

[0ion9]

+1. There are other ways of tracking renames -- for example by hash, like tmsu repair does -- but this is a common task, which really belongs in core TMSU imo.

[oniony]

Hi,

You can easily create a script that does this:

mv $1 $2 && tmsu repair --manual $1 $2

Thanks
Paul

Since tmsu doesn't explicitly monitor filesystem changes, it'd be nice if
there were an analogue of git mv - a move command that also adds the move
to the staging area - for tmsu, that would move the file while updating the
database so that no tag info is lost.

—
Reply to this email directly or view it on GitHub
#11.

[coldfix]

Hey, I think this might still be worth adding as a "porcelaine" command. Inexperienced users won't be able to guess tmsu repair --manual and will try to tmsu mv instead. Or maybe provide the possibility for aliases and define mv accordingly.

[oniony]

The problem I have with it is that no commands in TMSU currently make any
modifications on disk*: right now you can trust that TMSU will never modify
your files. Adding a 'mv' command would change this and this changes the
whole relationship with the tool.

I think, as its so easy to alias this in the shell, that its not necessary.
If there's enough demand, however, I would be open to changing my position
on this.

Thanks,
Paul

• other than to the database file

On Sat, 20 Dec 2014 16:50 Thomas G. [email protected] wrote:

Hey, I think this might still be worth adding as a "porcelaine" command.
Inexperienced users won't be able to guess tmsu repair --manual and will
try to tmsu mv instead. Or maybe provide the possibility for aliases and
define mv accordingly.

—
Reply to this email directly or view it on GitHub
#11 (comment).

[oniony]

Please leave a +1 comment on this if you would like to see 'mv' subcommand:

$ tmsu mv /old/path /new/path

Which would be equivalent to:

$ mv /old/path /new/path && tmsu repair --manual /old/path /new/path

[coldfix]

I'd vote rather for some checked version similar to this: (;but maybe not implemented in shell;)

(
 ([[ -e /new/path ]] && ! [[ -e /old/path ]]) ||
 (! [[ -e /new/path ]] && mv /old/path /new/path)
) &&
tmsu repair --manual /old/path new/path

Making 'mv' a short and easy to remember fix when the file was already moved on disk.