mirror of https://github.com/mpv-player/mpv
manpage: ipc: make requirements for newlines more explicit
Clarifying because someone asked.
This commit is contained in:
parent
6c2f25a7b0
commit
2a2391d3d8
|
@ -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
|
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.
|
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
|
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
|
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
|
(or ``mpv_command_string()`` in the client API). Additionally, line starting
|
||||||
|
|
Loading…
Reference in New Issue