You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the modify command's select mode, because it means you don't have to write super-specific queries - instead you can write a more general query and then simply type an n to skip those tracks you don't want to retag.
Unfortunately, there seems to be no way to "skip remaining tracks". For example, say I got through 50 out of 100 tracks that a query returned. I've answered y to most of them, but n to just a few. If I hit Ctrl-C at this point, I notice that the tags do not get written to the tracks I answered y to.
Perhaps we could add an s option that skips remaining tracks but still updates those that we answered y to. Alternatively, we could update tracks as-and-when we answer y, allowing us to Ctrl-C out of the process without losing work.
The text was updated successfully, but these errors were encountered:
sampsyo
changed the title
beet modify in select mode should allow you to "skip remaining tracks" and yet still write tags to those tracks already answered with y
Selection interface: option to "skip remaining tracks" and take action
Nov 27, 2018
Problem
I love the
modify
command's select mode, because it means you don't have to write super-specific queries - instead you can write a more general query and then simply type ann
to skip those tracks you don't want to retag.Unfortunately, there seems to be no way to "skip remaining tracks". For example, say I got through 50 out of 100 tracks that a query returned. I've answered
y
to most of them, butn
to just a few. If I hit Ctrl-C at this point, I notice that the tags do not get written to the tracks I answeredy
to.Perhaps we could add an
s
option that skips remaining tracks but still updates those that we answeredy
to. Alternatively, we could update tracks as-and-when we answery
, allowing us to Ctrl-C out of the process without losing work.The text was updated successfully, but these errors were encountered: