Eli Zaretskii writes: >> From: Spencer Baugh >> Cc: 70217@debbugs.gnu.org, monnier@iro.umontreal.ca >> Date: Tue, 28 May 2024 10:39:52 -0400 >> >> Eli Zaretskii writes: >> >> >> b/c does match bbb/ccc at the beginning, according to the >> >> partial-completion rules. Explained as a glob, partial-completion turns >> >> b/c into b*c which then can expand to bbb/ccc. >> > >> > Sorry, I don't understand what you are saying and how it addresses my >> > concern. To me, this example contradicts what was explained in the >> > documentation earlier, so we must clarify this, whether in the example >> > or in the preceding descriptions. Please re-read how you described >> > the effect of this option, and go from there. >> >> Okay, how about this completely reworked explanation? (It also changes >> the name of the variable and inverts its effect) > > Thanks, this is more clear now. > [snip] > and (b) please do not use examples with repeated characters, because > they can lead readers to make the wrong conclusions due to accidental > situations. For example, AFAIU valid candidates for "b*/c*" include > "bcdxyz/c1234" and also "b/x/y/z/c/1/2/3", but readers might > mistakenly think that "b*" stands for a string made only of "b", or > that there can be only one slash and it must precede "c". Avoiding > repeated characters prevents such misunderstandings. Excellent point, fixed. > But please (a) don't use "glob" and file wildcard notation, use > regexps instead; True, I removed the word "glob", I agree that's confusing since e.g. [a-z] or {foo,bar} are valid globs but not valid in partial-completion. Note however that "*" is literally valid syntax with partial-completion, where as the regexp notation (".*") is not. The partial-completion documentation already mentions this in (info "(emacs) Completion Styles"). So I slightly reworded it and continued using "*".