-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More helpful message than "moving 0 albums" #3117
Comments
Good call; this would be a useful thing to print. |
master...RollingStar:verbose-move Here it is in action, with different output depending on if there are any objects filtered out.
I think I have some work to do on my forked repo to not make this change have six git commits attached to it. Then I can submit a PR. |
Awesome! Thank you!! May I suggest some slightly simpler wording: for example, “15 already in place”? |
Good idea. |
Problem
When running beet mv, beets filters the move job to remove any move operations that have the same source and destination. But this can be unintuitive: albums will show up in "beet ls" then vanish when you run "beet mv".
beets/beets/ui/commands.py
Line 1485 in 9556ab3
Proposed Solution
Save the results of
objs
into something likeorig_objs
and compare it toobjs
after the filter operation is complete. The new output message could be something like:The text was updated successfully, but these errors were encountered: