From dbc41ea3bbf48bc5d7dd625fb7930b4a3b498cf7 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 1 Nov 2014 15:36:30 +0100 Subject: ipc: make it possible to receive log messages The receiving part was implemented, but since no messages are enabled by default, it couldn't be used. --- DOCS/man/ipc.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'DOCS/man') diff --git a/DOCS/man/ipc.rst b/DOCS/man/ipc.rst index 2b5b3d2156..f1e466a497 100644 --- a/DOCS/man/ipc.rst +++ b/DOCS/man/ipc.rst @@ -146,6 +146,16 @@ extra commands can also be used as part of the protocol: { "command": ["unobserve_property", 1] } { "error": "success" } +``request_log_messages`` + Enable output of mpv log messages. They will be received as events. The + parameter to this command is the log-level (see ``mpv_request_log_messages`` + C API function). + + Log message output is meant for humans only (mostly for debugging). + Attempting to retrieve information by parsing these messages will just + lead to breakages with future mpv releases. Instead, make a feature request, + and ask for a proper event that returns the information you need. + ``suspend`` Suspend the mpv main loop. There is a long-winded explanation of this in the C API function ``mpv_suspend()``. In short, this prevents the player -- cgit v1.2.3