summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2014-10-19 21:44:34 +0200
committerwm4 <wm4@nowhere>2014-10-19 22:34:37 +0200
commit2cd25891b67d4fb5c5afcad2bf0a6187b2b03b23 (patch)
tree8d4c83f5882260a26c3568cd8da40cf186096df5
parentd089772b69807b0a66e56f6501d2ecf3d70e0114 (diff)
downloadmpv-2cd25891b67d4fb5c5afcad2bf0a6187b2b03b23.tar.bz2
mpv-2cd25891b67d4fb5c5afcad2bf0a6187b2b03b23.tar.xz
manpage: ipc: mention the socat tool
This is not realy obvious, so I assume this is a helpful hint. Although the usefulness of such an approach is probably influenced by the fact that the player might send events that arrive in the short window while the socket is connected.
-rw-r--r--DOCS/man/ipc.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/DOCS/man/ipc.rst b/DOCS/man/ipc.rst
index e377e2e881..4666e7367e 100644
--- a/DOCS/man/ipc.rst
+++ b/DOCS/man/ipc.rst
@@ -4,7 +4,8 @@ JSON IPC
mpv can be controlled by external programs using the JSON-based IPC protocol. It
can be enabled by specifying the path to a unix socket using the option
``--input-unix-socket``. Clients can connect to this socket and send commands to
-the player or receive events from it.
+the player or receive events from it. You can use the ``socat`` tool to send
+commands (and receive reply) from the shell.
.. warning::