Re: Wildcard matching in debbugs-gnu-search - how?

[Michael Heerdegen <michael_heerdegen@web.de>]

Michael Albinus <michael.albinus@gmx.de> writes:

> Thanks! I've also tried to clarify in the debbugs user guide.

Great, thanks for working on that.

> The text reads now
>
>  -- Command: debbugs-gnu-search
>  -- Command: debbugs-org-search
>
>      These both commands are completely interactive.  They ask for a
>      '"search phrase"' for the text search.  It is just a string which
>      contains the words to be searched for followed by each other.
>      There are also operators like "AND", "ANDNOT" and "OR", which

FWIW; that still sounds a bit like multiple words could be given without
an operator for me.

>      If there is no operator between the wildcards, "AND" is used by
>      default.

And that even more.  Didn't we want to remove this?

> Unfortunately, hyperestraier does not speak about the syntax of a word,
> nowhere. Since it is written in Ruby, I guess it uses the syntax of a
> Ruby identifier, see
> <https://ruby-doc.org/docs/ruby-doc-bundle/Manual/man-1.4/syntax.html#ident>:
>
> Ruby identifiers are consist of alphabets, decimal digits, and the
> underscore character, and begin with a alphabets(including
> underscore). There are no restrictions on the lengths of Ruby
> identifiers.
>
> This explains, why your example "[RX] ^el-search-.*-sources$" does not
> work. Dashes don't belong to word syntax.

Ok.  Too bad you are not sure.  I guess many people wonder what a "word"
is in this context.


Regards,

Michael.