summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-11-30 22:22:09 +0100
committerwm4 <wm4@nowhere>2015-11-30 22:22:09 +0100
commite1d414c9922e79dfc3f00a1def679358e76ded69 (patch)
tree5c3452daad620660595e4ee845ea488dc2e8ed82
parent7f3cf75c5abae1de389ae0cc12cd165248512a7e (diff)
downloadmpv-e1d414c9922e79dfc3f00a1def679358e76ded69.tar.bz2
mpv-e1d414c9922e79dfc3f00a1def679358e76ded69.tar.xz
manpage: ' can't be used for quoting
-rw-r--r--DOCS/man/mpv.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/DOCS/man/mpv.rst b/DOCS/man/mpv.rst
index fda4aa0701..dd81392b6e 100644
--- a/DOCS/man/mpv.rst
+++ b/DOCS/man/mpv.rst
@@ -258,7 +258,7 @@ parser puts several options into a single string, and passes them to a
component at once, instead of using multiple options on the level of the
command line.
-The suboption parser can quote strings with ``"``, ``'``, and ``[...]``.
+The suboption parser can quote strings with ``"`` and ``[...]``.
Additionally, there is a special form of quoting with ``%n%`` described below.
For example, the ``opengl`` VO can take multiple options:
@@ -410,7 +410,7 @@ Escaping spaces and special characters
This is done like with command line options. The shell is not involved here,
but option values still need to be quoted as a whole if it contains certain
-characters like spaces. A config entry can be quoted with ``"`` and ``'``,
+characters like spaces. A config entry can be quoted with ``"``,
as well as with the fixed-length syntax (``%n%``) mentioned before. This is like
passing the exact contents of the quoted string as command line option. C-style
escapes are currently _not_ interpreted on this level, although some options do