Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2026-01-30 20:13:37 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #354 from mineo/docs-fixup-2

Browse source 
Docs fixup
This commit is contained in:
Adrian Sampson 2013-08-06 09:46:14 -07:00
commit bb191e7ced
4 changed files with 11 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/tagger.rst
View file

@ -262,7 +262,7 @@ If you think beets is ignoring an album that's listed in MusicBrainz, please
I Hope That Makes Sense
-----------------------
I haven't made the process clear, please `drop me an email`_ and I'll try to
If I haven't made the process clear, please `drop me an email`_ and I'll try to
improve this guide.
.. _drop me an email: mailto:adrian@radbox.org

2
docs/plugins/inline.rst
View file

@ -3,7 +3,7 @@ Inline Plugin
The ``inline`` plugin lets you use Python to customize your path formats. Using
it, you can define template fields in your beets configuration file and refer
to them from your template strings in the ``[paths]`` section (see
to them from your template strings in the ``paths:`` section (see
:doc:`/reference/config/`).
To use inline field definitions, first enable the plugin by putting ``inline``

14
docs/plugins/zero.rst
View file

@ -6,12 +6,12 @@ can be nulled unconditionally or conditioned on a pattern match. For example,
the plugin can strip useless comments like "ripped by MyGreatRipper." This
plugin only affects files' tags; the beets database is unchanged.
To use plugin, enable it by including ``zero`` into ``plugins`` line of your
configuration file. To configure the plugin, use a ``zero:`` section in your
configuration file. Set ``fields`` to the (whitespace-separated) list of fields
to change. You can get the list of available fields by running ``beet fields``.
To conditionally filter a field, use ``field: [regexp, regexp]`` to specify
regular expressions.
To use the plugin, enable it by including ``zero`` in the ``plugins`` line of
your configuration file. To configure the plugin, use a ``zero:`` section in
your configuration file. Set ``fields`` to the (whitespace-separated) list of
fields to change. You can get the list of available fields by running ``beet
fields``. To conditionally filter a field, use ``field: [regexp, regexp]`` to
specify regular expressions.
For example::
@ -20,7 +20,7 @@ For example::
comments: [EAC, LAME, from.+collection, 'ripped by']
genre: [rnb, 'power metal']
If custom pattern is not defined for a given field, the field will be nulled
If a custom pattern is not defined for a given field, the field will be nulled
unconditionally.
Note that the plugin currently does not zero fields when importing "as-is".

4
docs/reference/cli.rst
View file

@ -59,7 +59,7 @@ right now; this is something we need to work on. Read the
* During a long tagging import, it can be useful to keep track of albums
that weren't tagged successfully---either because they're not in the
MusicBrainz database or because something's wrong with the files. Use the
``-l`` option to specify a filename to log every time you skip and album
``-l`` option to specify a filename to log every time you skip an album
or import it "as-is" or an album gets skipped as a duplicate.
* Relatedly, the ``-q`` (quiet) option can help with large imports by
@ -86,7 +86,7 @@ right now; this is something we need to work on. Read the
``incremental`` configuration option.
* By default, beets will proceed without asking if it finds a very close
metadata match. To disable this and have the importer as you every time,
metadata match. To disable this and have the importer ask you every time,
use the ``-t`` (for *timid*) option.
* The importer typically works in a whole-album-at-a-time mode. If you