summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-03-23 17:41:19 +0100
committerwm4 <wm4@nowhere>2015-03-23 17:41:19 +0100
commit2a2391d3d86891721b3344341d1627a07f60e934 (patch)
tree2de0ebf935604d508fbbc46f443aa3f756f37c68
parent6c2f25a7b0271fd901f946324ea3b850bebc290a (diff)
downloadmpv-2a2391d3d86891721b3344341d1627a07f60e934.tar.bz2
mpv-2a2391d3d86891721b3344341d1627a07f60e934.tar.xz
manpage: ipc: make requirements for newlines more explicit
Clarifying because someone asked.
-rw-r--r--DOCS/man/ipc.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/DOCS/man/ipc.rst b/DOCS/man/ipc.rst
index 0edec05066..bbe07f0aba 100644
--- a/DOCS/man/ipc.rst
+++ b/DOCS/man/ipc.rst
@@ -79,6 +79,9 @@ mpv will also send events to clients with JSON messages of the following form:
where ``event_name`` is the name of the event. Additional event-specific fields
can also be present. See `List of events`_ for a list of all supported events.
+All commands, replies, and events are separated from each other with a line
+break character (``\n``).
+
If the first character (after skipping whitespace) is not ``{``, the command
will be interpreted as non-JSON text command, as they are used in input.conf
(or ``mpv_command_string()`` in the client API). Additionally, line starting