Update examples in docs to reflect new UI enhancements.

This commit is contained in:
Tai Lee 2013-05-27 01:25:13 +10:00
parent 799c85f380
commit 7700eaee79
2 changed files with 12 additions and 9 deletions

View file

@ -8,12 +8,13 @@ It then provides a bouquet of tools for manipulating and accessing your music.
Here's an example of beets' brainy tag corrector doing its thing::
$ beet import ~/music/ladytron
Tagging: Ladytron - Witching Hour
Tagging:
Ladytron - Witching Hour
(Similarity: 98.4%)
* Last One Standing -> The Last One Standing
* Beauty -> Beauty*2
* Last One Standing -> The Last One Standing
* Beauty -> Beauty*2
* White Light Generation -> Whitelightgenerator
* All the Way -> All the Way...
* All the Way -> All the Way...
Because beets is designed as a library, it can do almost anything you can
imagine for your music collection. Via `plugins`_, beets becomes a panacea:

View file

@ -113,12 +113,13 @@ Similarity
So you import an album into your beets library. It goes like this::
$ beet imp witchinghour
Tagging: Ladytron - Witching Hour
Tagging:
Ladytron - Witching Hour
(Similarity: 98.4%)
* Last One Standing -> The Last One Standing
* Beauty -> Beauty*2
* Last One Standing -> The Last One Standing
* Beauty -> Beauty*2
* White Light Generation -> Whitelightgenerator
* All the Way -> All the Way...
* All the Way -> All the Way...
Here, beets gives you a preview of the album match it has found. It shows you
which track titles will be changed if the match is applied. In this case, beets
@ -138,7 +139,8 @@ Choices
When beets needs your input about a match, it says something like this::
Tagging: Beirut - Lon Gisland
Tagging:
Beirut - Lon Gisland
(Similarity: 94.4%)
* Scenic World (Second Version) -> Scenic World
[A]pply, More candidates, Skip, Use as-is, as Tracks, Enter search, or aBort?