Cannot use the input-conf option from within an extension Auto Profile.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv version and platform
0.28.2
Reproduction steps
in mpv.conf:
[extension.jpg]
input-conf=~~/test-input.conf
[regular-profile]
input-conf=~~/test-input.conf
in test-input.conf:
ESC quit
Invoke mpv: mpv test.jpg
Expected behavior
When mpv is invoked on a jpg file, the [extension.jpg] profile should load the test-input.conf input config file. (Note that if the [extension.jpg] profile is commented out and mpv is invoked as mpv --profile=regular-profile test.jpg the input-conf line works as expected)
Or if this isn't possible for some reason, a more explanatory error message should be printed.
Actual behavior
Auto-loading profile 'extension.jpg'
Error parsing option input-conf (option parameter could not be parsed)
Log file
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
Reproduce the issue with mpv test.jpg using the shown mpv.conf and test-input.conf, then inspect the extension.jpg profile loading and input-conf option parsing paths. Done means the input config loads for the auto profile, or the failure produces a more explanatory error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100