From 9e972ed7d28c33bf612452682f229fa14ef017ea Mon Sep 17 00:00:00 2001 From: wm4 Date: Sun, 18 Sep 2016 13:38:45 +0200 Subject: options: rename/deprecate --playlist-pos Conflicts with the "playlist-pos" property. They're really a bit too different, and since the --playlist-pos option is relatively new and obscure, just rename it to get this out of the way. --- DOCS/man/input.rst | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'DOCS/man/input.rst') diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst index c7c7c0d887..e626b1ba81 100644 --- a/DOCS/man/input.rst +++ b/DOCS/man/input.rst @@ -2122,12 +2122,6 @@ caveats with some properties (due to historical reasons): option is for loading playlist during command line parsing. For client API uses, you should use the ``loadlist`` command instead. -``playlist-pos`` - The property refuses setting out of range values, restarts playback - immediately when writing to it, and does not know the ``no`` value (which - the option uses to indicate the default state, that is resuming a file - on the playlist and jumping to that instead of entry 0). - ``audio-file``, ``sub-file``, ``external-file`` These options/properties are actually lists of filenames. To make the command-line interface easier, each ``--audio-file=...`` option appends @@ -2141,7 +2135,7 @@ caveats with some properties (due to historical reasons): Strictly speaking, option access via API (e.g. ``mpv_set_option_string()``) has the same problem, and it's only a difference between CLI/API. -``demuxer``, ``idle``, ``length``, ``audio-samplerate``, ``audio-channels``, ``audio-format``, ``fps``, ``cache`` +``demuxer``, ``idle``, ``length``, ``audio-samplerate``, ``audio-channels``, ``audio-format``, ``fps``, ``cache``, ``playlist-pos`` These behave completely different as property, but are deprecated (newer aliases which don't conflict have been added). After the deprecation period they will be changed to the proper option behavior. -- cgit v1.2.3