From: Michael Heerdegen <michael_heerdegen@web.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Wildcard matching in debbugs-gnu-search - how?
Date: Sun, 06 Oct 2019 12:08:05 +0200 [thread overview]
Message-ID: <87sgo61916.fsf@web.de> (raw)
In-Reply-To: <87muefcbac.fsf@gmx.de> (Michael Albinus's message of "Sat, 05 Oct 2019 20:11:39 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> I've tested the HyperEstraier search engine using
> <https://debbugs.gnu.org/cgi/search.cgi>, and it looks you are
> right. Compare the search for "[BW] gcc AND [EW] gforth" and "[BW] gcc
> [EW] gforth". So I have adapted the debbugs-ug manual, again.
Thank you very much. Looks good!
I didn't notice that - until I read your adaption, that a sequence of
words matches the same sequence of words (in the same order). Should we
speak that out more explicitly? Though, I understood it.
BTW, it seems that non-(Ruby) word chars are not just ignored. For
example, with the query "el-search-emacs-elisp-sources" I find Bug#37321
(expected) but with "el search emacs elisp sources" I don't get a match
(unexpected for me). Do you know more?
> I hope it will get better with your Weisheistszaehne!
You mean without :-P
> Wish you the best!
Thank you! I'm already quite well again.
Regards,
Michael.
next prev parent reply other threads:[~2019-10-06 10:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 10:38 Wildcard matching in debbugs-gnu-search - how? Michael Heerdegen
2019-09-24 11:32 ` Michael Albinus
2019-09-24 11:51 ` Michael Heerdegen
2019-09-24 12:00 ` Michael Albinus
2019-09-24 12:29 ` Michael Heerdegen
2019-09-24 13:01 ` Michael Albinus
2019-10-04 16:47 ` Michael Heerdegen
2019-10-05 10:27 ` Michael Albinus
2019-10-05 11:50 ` Michael Heerdegen
2019-10-05 12:01 ` Michael Albinus
2019-10-05 17:20 ` Michael Heerdegen
2019-10-05 18:11 ` Michael Albinus
2019-10-06 10:08 ` Michael Heerdegen [this message]
2019-10-06 10:31 ` Michael Albinus
2019-10-06 10:38 ` Michael Heerdegen
2019-10-16 11:57 ` Michael Heerdegen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgo61916.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).