diff options
| author | wm4 <wm4@nowhere> | 2017-04-10 21:19:13 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2017-04-10 21:19:13 +0200 |
| commit | 6dea8fceda981481798f6f492db54c6fd8708c3b (patch) | |
| tree | 909de256cf9fd15602eb1f37eff72eedbb1c7acc /options/options.c | |
| parent | 759ac6cc93bd1895a8f9233b8e9256889bdef6aa (diff) | |
| download | mpv-6dea8fceda981481798f6f492db54c6fd8708c3b.tar.bz2 mpv-6dea8fceda981481798f6f492db54c6fd8708c3b.tar.xz | |
options: deprecate --loop
Also "announce" the plans to undeprecate it with changed semantics
later. The deprecation period is needed to warn script authors and
client API users (etc.) of the change.
This is done because everyone seems to expect --loop to loop the current
file, not the playlist. Even in cases when only 1 file is on the
playlist, the --loop-file semantics seem to be preferred.
Diffstat (limited to 'options/options.c')
| -rw-r--r-- | options/options.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/options/options.c b/options/options.c index 5333cf406c..c595964121 100644 --- a/options/options.c +++ b/options/options.c @@ -607,7 +607,7 @@ const m_option_t mp_opts[] = { OPT_FLAG("stop-playback-on-init-failure", stop_playback_on_init_failure, 0), - OPT_CHOICE_OR_INT("loop", loop_times, 0, 1, 10000, + OPT_CHOICE_OR_INT("loop-playlist", loop_times, 0, 1, 10000, ({"no", 1}, {"inf", -1}, {"yes", -1}, {"force", -2})), @@ -832,6 +832,8 @@ const m_option_t mp_opts[] = { OPT_REPLACED("ass-style-override", "sub-ass-style-override"), OPT_REPLACED("ass-scale-with-window", "sub-ass-scale-with-window"), OPT_REMOVED("fs-black-out-screens", NULL), + OPT_REPLACED_MSG("loop", "loop-playlist", "--loop will be changed to map to" + " --loop-file in future releases."), {0} }; |