summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-11-21 22:43:48 +0100
committerwm4 <wm4@nowhere>2019-11-22 01:15:08 +0100
commiteab5457e47389d5eeb79010f2f35e4d6613df86f (patch)
tree092086783fe70c198e0c73c0b4854a8598753ab7
parenta394d9e3aeadb0a2dedd7c15d8322252742b2fe4 (diff)
downloadmpv-eab5457e47389d5eeb79010f2f35e4d6613df86f.tar.bz2
mpv-eab5457e47389d5eeb79010f2f35e4d6613df86f.tar.xz
manpage: correct "complex" key binding description
The key is never nil if it's invoked through the normal input path. The key name could be "" if mp_cmd.key_name==NULL. This should not happen, but there's no strong guarantee in input.c that it cannot happen, so whatever.
-rw-r--r--DOCS/man/lua.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/DOCS/man/lua.rst b/DOCS/man/lua.rst
index 13cd3dbad0..8861552562 100644
--- a/DOCS/man/lua.rst
+++ b/DOCS/man/lua.rst
@@ -262,8 +262,8 @@ The ``mp`` module is preloaded, although it can be loaded manually with
Boolean Whether the event was caused by a mouse button.
``key_name``
- The name of they key that triggered this, or ``nil`` if unknown
- or invoked artificially.
+ The name of they key that triggered this, or ``nil`` if invoked
+ artificially. If the key name is unknown, it's an empty string.
Internally, key bindings are dispatched via the ``script-message-to`` or
``script-binding`` input commands and ``mp.register_script_message``.