doc/protocol.rst: remove documentation about `==` matching substrings
I added this sentence in commit5271e81ebe
, but this was merely documented the legacy status quo, which has always been undocumented for old-style filters. But for new filters, using "==" for sub strings was a surprising "feature", which I removed in commitac0852b4e3
.
This commit is contained in:
parent
228bf7eb09
commit
0b0f4c61f1
|
@ -152,10 +152,7 @@ of:
|
|||
``VALUE`` in ``AlbumArtist``
|
||||
and falls back to ``Artist`` tags if
|
||||
``AlbumArtist`` does not exist.
|
||||
``VALUE`` is what to find. The
|
||||
`find` commands specify an exact value
|
||||
and are case-sensitive; the `search`
|
||||
commands specify a sub string and ignore case.
|
||||
``VALUE`` is what to find.
|
||||
|
||||
- ``(TAG =~ 'VALUE')`` and ``(TAG !~ 'VALUE')`` use a Perl-compatible
|
||||
regular expression instead of doing a simple string comparison.
|
||||
|
@ -189,6 +186,9 @@ of:
|
|||
be enclosed in parantheses, e.g. :code:`((artist == 'FOO') AND
|
||||
(album == 'BAR'))`
|
||||
|
||||
The :command:`find` commands are case sensitive, which
|
||||
:command:`search` and related commands ignore case.
|
||||
|
||||
Prior to MPD 0.21, the syntax looked like this::
|
||||
|
||||
find TYPE VALUE
|
||||
|
|
Loading…
Reference in New Issue