# HG changeset patch
# User Markus Mützel <markus.muetzel@gmx.de>
# Date 1650558693 -7200
# Node ID c09fdabaa5b6f79922d9b1c25dc8370be0ca2b52
# Parent  6397b6d7c42e1beb7b802548fa3247ca3394cade
dir.m: Clarify wildcard behavior on Windows in docstring (bug #62282).

diff -r 6397b6d7c42e -r c09fdabaa5b6 scripts/miscellaneous/dir.m
--- a/scripts/miscellaneous/dir.m	Thu Apr 21 18:30:25 2022 +0200
+++ b/scripts/miscellaneous/dir.m	Thu Apr 21 18:31:33 2022 +0200
@@ -61,9 +61,13 @@
 ## than a single directory or file.
 ##
 ## @var{directory} is subject to shell expansion if it contains any wildcard
-## characters @samp{*}, @samp{?}, @samp{[]}.  To find a literal example of a
-## wildcard character the wildcard must be escaped using the backslash operator
-## @samp{\}.
+## characters @samp{*}, @samp{?}, @samp{[]}.  If these wildcard characters are
+## escaped with a backslash @samp{\} (e.g., @samp{\*}) on a POSIX platform,
+## they aren't treated as wildcards but as the corresponding literal character.
+## On Windows, it is not possible to escape wildcard characters because
+## backslash @samp{\} is treated as a file separator.  On Windows, use
+## @code{ls} instead for file or folder names that contain characters that
+## would be treated as wildcards by @code{dir}.
 ##
 ## Note that for symbolic links, @code{dir} returns information about the
 ## file that the symbolic link points to rather than the link itself.