diff options
| author | wm4 <wm4@nowhere> | 2019-07-07 20:39:58 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2019-09-19 20:37:05 +0200 |
| commit | 9d97c4d814bc63b456513c9a0e8c0ee4fd47a2c5 (patch) | |
| tree | 9fb4eefcc9b705755f002217c53caf55c2acb3ac /DOCS | |
| parent | 023b5964b047d83772163195c322936968e7d47a (diff) | |
| download | mpv-9d97c4d814bc63b456513c9a0e8c0ee4fd47a2c5.tar.bz2 mpv-9d97c4d814bc63b456513c9a0e8c0ee4fd47a2c5.tar.xz | |
manpage: mention that there's a Lua API for async commands
But don't tell the reader which those APIs are. Hope the user will just
search for "async" in the Lua section (lua.rst). But of course, nobody
will ever care about anything related to this.
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/man/input.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst index 7c40a5cd43..fdbe4e5fd8 100644 --- a/DOCS/man/input.rst +++ b/DOCS/man/input.rst @@ -1130,6 +1130,8 @@ command behaves by itself. There are the following cases: - Async libmpv command API (e.g. ``mpv_command_async()``) never blocks the caller, and always notify their completion with a message. The ``sync`` and ``async`` prefixes make no difference. +- Lua also provides APIs for running async commands, which behave similar to the + C counterparts. - In all cases, async mode can still run commands in a synchronous manner, even in detached mode. This can for example happen in cases when a command does not have an asynchronous implementation. The async libmpv API still never blocks |