From ac01e6a14705c8d747d9ce5e2282c134bc9293de Mon Sep 17 00:00:00 2001 From: wm4 Date: Wed, 6 Nov 2013 20:27:19 +0100 Subject: input.conf: clarify the magic how default key bindings are added This is a confusing mechanism, so the explanation should bit more clear. --- etc/input.conf | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'etc') diff --git a/etc/input.conf b/etc/input.conf index 1687220d08..432444f753 100644 --- a/etc/input.conf +++ b/etc/input.conf @@ -31,9 +31,13 @@ # file to ~/.mpv/input.conf, and uncomment and edit the binding you want to # change. -# Developer note: this file is baked into the mpv binary, and internally, -# entries are uncommented and added as default bindings. Lines that have a -# space after the '#' are ignored. +# Developer note: +# etc/input.conf from the mpv source tree is baked into the mpv binary, with +# all entries magically uncommented and parsed on initialization. This, this +# file defines the mpv default key bindings. If this file is read as normal +# config file, all lines starting with '#' are treated as comments (and this +# file, if unedited, doesn't define any bindings). +# Lines that have a space after the '#' are always ignored as real comments. #MOUSE_BTN0 ignore # don't do anything #MOUSE_BTN0_DBL cycle fullscreen # toggle fullscreen on/off -- cgit v1.2.3