Open flight16 opened 9 years ago
Thanks for the request. This seems reasonable.
Right now the pretend mode skips all parts of the import process, and just prints the files selected. Very basic, and little informative.
Would it not be more expected behavior to have the importer run and group the albums, look up the candidates, and then print out what would happen to the files ?
This way a user would experience the actual importing process, without fear of making changes to his filesystem / the database.
Absolutely, although I can at the moment see uses for both. This feature was originally created to check whether filtering and such were yielding the right set of files; that's probably best served by something that just quickly lists out paths. But you're right that it might also be useful to run the whole, slow process and just skip the actual importing.
I'm not sure whether that calls for another new config option or just something like a "forced action" where the action can be "skip".
Just spitballing here, but let's say:
--pretend
runs the whole slow tagging process, but doesn't touch the database, nor the files.-v
will show it)-v
will show it)Use cases:
$ beet -v import --pretend -A .
This will also show how the files will be moved (and thus cover this issues' use-case). $ beet import --pretend
$ beet -v import --pretend
This seems eminently reasonable! And no new flag required.
It seems like the implementation should be fairly straightforward too, right? Just check in the appropriate pipeline stages and suppress action, rather than dropping the tasks altogether as we do now.
Yeah, barring any unforseen special cases, it should be little work. I'll get something up tomorrow, probably.
Sorry I've been MIA! Gotta focus on finishing thesis before I can start work on beets again.
@tomjaspers Hey, me too! :smiley: https://github.com/sampsyo/thesis
Background
I want to see the destination of an import so I know I didn't make a mistake that will send my music collection sprawling across my hdd.
I have a large directory of perfectly tagged files. I simply want to import them to beets and move them to directories based on their tags.
Commands executed, output displayed
That output doesn't isn't useful to me. It doesn't allow me to verify the files will go where I think they will go, that the files have all of the metadata to be used for the path template, and that I don't have any errors in my path template.
Whoops! Syntax error in my path template caused my files to go to the wrong destination.
What I expected to see
Or if beets detects my terminal isn't wide enough
I also expect to see the above when I run the command for real.
(This isn't some made-up example. It was honestly my very first experience with beets 5 minutes ago.)