From eab5457e47389d5eeb79010f2f35e4d6613df86f Mon Sep 17 00:00:00 2001
From: wm4 <wm4@nowhere>
Date: Thu, 21 Nov 2019 22:43:48 +0100
Subject: [PATCH] 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.
---
DOCS/man/lua.rst | 4 ++--
1 file 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``.