input.conf: clarify the magic how default key bindings are added

This is a confusing mechanism, so the explanation should bit more clear.
This commit is contained in:
wm4 2013-11-06 20:27:19 +01:00
parent ce8bc1320d
commit ac01e6a147
1 changed files with 7 additions and 3 deletions

View File

@ -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