Feature: Please include built-in hotkeys in an included default input.conf, with other possible functions commented out
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Expected behavior of the wanted feature
By default, at least on Windows and MacOS, there is no input.conf anywhere, so after doing further reading you have to make one (and its location isn't clear as it doesn't account for portable installs, for example).
Additionally there are some hotkeys "built in" to MPV, which needs separate reading to find and discover.
A nice QOL feature would be to just include an input.conf with the application, in a location where mpv will look for it (so I assume .\mpv\input.conf will do), with enabled functions and hotkeys listed and available ones commented out.
I am aware that it's possible to list supported keys in mpv, but bonus points if somewhere in the input.conf there's a list of supported keys, so that questions like "how can I make ` or CAPS LOCK a hotkey?", or "Will my hotkeys override the built in ones?", or "How do I change existing hotkeys?" can get answered without having to scour documentation.
Alternative behavior of the wanted feature
No response
Log File
No response
Sample Files
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how mpv locates input.conf, including the proposed .\mpv\input.conf location, and how built-in hotkeys and supported keys are documented. Define a cross-platform default configuration that includes the enabled bindings and commented alternatives, then verify that users can discover and override the bindings without scouring separate documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100