oysteikt
/
mpd
0
0
Fork 0
Code Issues Pull Requests Releases Activity

doc/protocol.rst: remove documentation about `==` matching substrings 

I added this sentence in commit
5271e81ebe, 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 commit
ac0852b4e3.
This commit is contained in:
Max Kellermann 2018-11-12 12:45:40 +01:00
parent 228bf7eb09
commit 0b0f4c61f1
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/protocol.rst
View File

@ -152,10 +152,7 @@ of:
``VALUE`` in ``AlbumArtist`` ``VALUE`` in ``AlbumArtist``
and falls back to ``Artist`` tags if and falls back to ``Artist`` tags if
``AlbumArtist`` does not exist. ``AlbumArtist`` does not exist.
``VALUE`` is what to find. The ``VALUE`` is what to find.
`find` commands specify an exact value
and are case-sensitive; the `search`
commands specify a sub string and ignore case.
- ``(TAG =~ 'VALUE')`` and ``(TAG !~ 'VALUE')`` use a Perl-compatible - ``(TAG =~ 'VALUE')`` and ``(TAG !~ 'VALUE')`` use a Perl-compatible
regular expression instead of doing a simple string comparison. regular expression instead of doing a simple string comparison.
@ -189,6 +186,9 @@ of:
be enclosed in parantheses, e.g. :code:`((artist == 'FOO') AND be enclosed in parantheses, e.g. :code:`((artist == 'FOO') AND
(album == 'BAR'))` (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:: Prior to MPD 0.21, the syntax looked like this::
find TYPE VALUE find TYPE VALUE