@@ -2,10 +2,8 @@ Zero Plugin
2
2
===========
3
3
4
4
The ``zero `` plugin allows you to null fields in files' metadata tags. Fields
5
- can be nulled unconditionally or conditioned on a pattern match. It works in
6
- two independent modes - blacklist and whitelist. You can only choose one option,
7
- however blacklist is the default. For example, the plugin can strip useless
8
- comments like "ripped by MyGreatRipper."
5
+ can be nulled unconditionally or conditioned on a pattern match. For example,
6
+ the plugin can strip useless comments like "ripped by MyGreatRipper."
9
7
10
8
To use the ``zero `` plugin, enable the plugin in your configuration
11
9
(see :ref: `using-plugins `).
@@ -20,9 +18,9 @@ fields to nullify and the conditions for nullifying them:
20
18
get the list of all available fields by running ``beet fields ``. In
21
19
addition, the ``images `` field allows you to remove any images
22
20
embedded in the media file.
23
- * Set ``keep_fields `` respectively to list of fields that plugin should
24
- preserve. That way `` zero `` cleans anything other than fields written in this
25
- option.
21
+ * Set ``keep_fields `` to * invert * the logic of the plugin. Only these fields
22
+ will be kept; other fields will be removed. Remember to set only
23
+ `` fields `` or `` keep_fields ``, not both!
26
24
* To conditionally filter a field, use ``field: [regexp, regexp] `` to specify
27
25
regular expressions.
28
26
* By default this plugin only affects files' tags ; the beets database is left
@@ -36,6 +34,10 @@ For example::
36
34
genre: [rnb, 'power metal']
37
35
update_database: true
38
36
37
+ The plugin can work in one of two modes. The first mode, the default,
38
+ is a blacklist, where you choose the tags you want to remove. The second mode
39
+ is a whitelist where you instead specify the tags you want to keep.
40
+
39
41
If a custom pattern is not defined for a given field, the field will be nulled
40
42
unconditionally.
41
43
0 commit comments