bug#60819: 28.2; `ls-lisp.el' regression introduced in Emacs 26

[Eli Zaretskii]

> From: Drew Adams <drew.adams@oracle.com>
> CC: "60819-done@debbugs.gnu.org" <60819-done@debbugs.gnu.org>
> Date: Sun, 15 Jan 2023 17:04:05 +0000
> 
> > > In general, the character / in a glob pattern cannot be matched by a
> > > wildcard.  E.g., Wikipedia says "Normally, the path separator character
> > > (/ on Linux/Unix, MacOS, etc. or \ on Windows) will never be matched."
> > > and Linux man page glob(7) says "A '/' in a pathname cannot be matched
> > > by a '?' or '*' wildcard, or by a range like "[.-0]"."
> > 
> > This is incorrect.  A wildcard like "*b*/" should expand to the list
> > of directories whose names match "*b*", whereas "*b*" should expand to
> > the list of files _and_ directories with matching names.  This is how
> > Dired behaves on Posix platforms (where such an expansion is done by
> > the 'ls' program), and we want a similar behavior with ls-lisp.
> 
> Excellent.  That's in fact what I was naively expecting
> or hoping for.
> 
> But googling for info about what such a glob pattern
> should match, I couldn't find anything that supported
> such an interpretation.  Could you maybe point me to a
> source that covers this - so I can read more and point
> others to it?  If you don't have the time to find that
> then don't worry about it.  Thx.

I'm not sure this should be documented in some special way.  Since a
wildcard match cannot cross a slash, it follows that a slash can only
match itself.  So you are looking for files whose names end in a
slash, and those by convention are directories, both in Emacs and with
GNU Coreutils.  Cf directory-name-p and file-name-as-directory.