Closed guidocella closed 19 hours ago
This never did anything because mp_input_load_config() always already called parse_config() with builtin = true for builtin_input_conf.
This is incorrect. For key bindings loaded from config files rather than builtin_input_conf
, this makes the bindings treated as builtin so they have lower priority compared to non-builtin bindings.
Ok but we don't have any such config file with that line.
It can be defined in user's config files.
But why would someone do that? It's not even documented.
But why would someone do that?
It has valid uses. For example, a mpv plugin or script can redefine builtin key bindings, without needing to recompile mpv, while still allowing user bindings in input.conf
take preference. It allows changing player key bindings in a less agressive way.
This reverts commit 70ff543029068188a3de39a80a764267c6671e7c.
This never did anything because mp_input_load_config() always already called parse_config() with builtin = true for builtin_input_conf. And we already have compatibility input.conf files without depending on this line. So unless someone can decipher what wm4 meant, it can be removed.