--merge-files doesn't work with per-file option
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Important Information
Provide following Information:
- mpv version
0.34.0-16-gec16769c2d - Platform and Version
Windows 10 19.43.1288 - Source of the mpv binary
shinchirol's build
If you're not using git master or the latest release, update.
Releases are listed here: https://github.com/mpv-player/mpv/releases
Reproduction steps
Run mpv --no-config --{ a.mkv b.mkv --merge-files --}
Expected behavior
The two files are merged into one file.
Actual behavior
There are two separated files in playlist.
BTW, if --merge-files is out of --{ }--, mpv --no-config --{ a.mkv b.mkv --} --merge-files for example, its behavior is as expected.
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 the two mpv --no-config --{ ... --} command forms and compare the attached working and failing logs. Trace the command-line handling of --merge-files and per-file options; done means the in-scope form merges a.mkv and b.mkv into one playlist entry while the existing outside-scope form still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100