From 4a336214dffbf6407401a6d71493499c4c3e50af Mon Sep 17 00:00:00 2001
From: Arcitec <38923130+Arcitec@users.noreply.github.com>
Date: Tue, 29 Oct 2024 18:37:01 +0100
Subject: [PATCH] DOCS/man/mpv: clarify config-dir path behavior

---
 DOCS/man/mpv.rst | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/DOCS/man/mpv.rst b/DOCS/man/mpv.rst
index 64de51d112c13..8cd7b253e2c0c 100644
--- a/DOCS/man/mpv.rst
+++ b/DOCS/man/mpv.rst
@@ -514,14 +514,17 @@ Currently, the prefix ``~~home/`` expands to the mpv configuration directory
 ``~/`` expands to the user's home directory. (The trailing ``/`` is always
 required.) The following paths are currently recognized:
 
+**Important:** Beware that if ``--no-config`` is used, then all of the "config
+directory"-based paths will resolve to an empty path prefix, meaning that both
+``~~/foobar`` and ``~~home/foobar`` will resolve to ``foobar``, which might not
+be what you expected.
+
 ================ ===============================================================
 Name             Meaning
 ================ ===============================================================
-``~~/``          If the subpath exists in any of the mpv's config directories
+``~~/``          If the subpath exists in any of mpv's config directories, then
                  the path of the existing file/dir is returned. Otherwise this
                  is equivalent to ``~~home/``.
-                 Note that if --no-config is used ``~~/foobar`` will resolve to
-                 ``foobar`` which can be unexpected.
 ``~/``           user home directory root (similar to shell, ``$HOME``)
 ``~~home/``      mpv config dir (for example ``~/.config/mpv/``)
 ``~~global/``    the global config path, if available (not on win32)