@@ -5,6 +5,10 @@ The ``zero`` plugin allows you to null fields in files' metadata tags. Fields
5
5
can be nulled unconditionally or conditioned on a pattern match. For example,
6
6
the plugin can strip useless comments like "ripped by MyGreatRipper."
7
7
8
+ The plugin can work in one of two modes. The first mode, the default, is a
9
+ blacklist, where you choose the tags you want to remove. The second mode is a
10
+ whitelist, where you instead specify the tags you want to keep.
11
+
8
12
To use the ``zero `` plugin, enable the plugin in your configuration
9
13
(see :ref: `using-plugins `).
10
14
@@ -20,7 +24,7 @@ fields to nullify and the conditions for nullifying them:
20
24
embedded in the media file.
21
25
* Set ``keep_fields `` to *invert * the logic of the plugin. Only these fields
22
26
will be kept; other fields will be removed. Remember to set only
23
- ``fields `` or ``keep_fields ``, not both!
27
+ ``fields `` or ``keep_fields ``--- not both!
24
28
* To conditionally filter a field, use ``field: [regexp, regexp] `` to specify
25
29
regular expressions.
26
30
* By default this plugin only affects files' tags ; the beets database is left
@@ -34,10 +38,6 @@ For example::
34
38
genre: [rnb, 'power metal']
35
39
update_database: true
36
40
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
-
41
41
If a custom pattern is not defined for a given field, the field will be nulled
42
42
unconditionally.
43
43
0 commit comments