From a07832313d382c2a6fce9477ce1067f125d94a2a Mon Sep 17 00:00:00 2001 From: James Ross-Gowan Date: Wed, 23 Mar 2016 23:01:57 +1100 Subject: man: ipc: update for named pipe IPC on Windows --- DOCS/man/options.rst | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'DOCS/man/options.rst') diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index 7280a3e6d3..d8de023a60 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -2440,7 +2440,7 @@ Input ``--input-file=`` Read commands from the given file. Mostly useful with a FIFO. Since mpv 0.7.0 also understands JSON commands (see `JSON IPC`_), but you can't - get replies or events. Use ``--input-unix-socket`` for something + get replies or events. Use ``--input-ipc-server`` for something bi-directional. On MS Windows, JSON commands are not available. This can also specify a direct file descriptor with ``fd://N`` (UNIX only). @@ -2460,12 +2460,18 @@ Input or intend to read from stdin later on via the loadfile or loadlist slave commands. -``--input-unix-socket=`` +``--input-ipc-server=`` Enable the IPC support and create the listening socket at the given path. - See `JSON IPC`_ for details. + On Linux and Unix, the given path is a regular filesystem path. On Windows, + named pipes are used, so the path refers to the pipe namespace + (``\\.\pipe\``). If the ``\\.\pipe\`` prefix is missing, mpv will add + it automatically before creating the pipe, so + ``--input-ipc-server=/tmp/mpv-socket`` and + ``--input-ipc-server=\\.\pipe\tmp\mpv-socket`` are equivalent for IPC on + Windows. - Not available on MS Windows. + See `JSON IPC`_ for details. ``--input-appleremote=`` (OS X only) -- cgit v1.2.3