unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Wildcard matching in debbugs-gnu-search - how?
Date: Sat, 05 Oct 2019 20:11:39 +0200	[thread overview]
Message-ID: <87muefcbac.fsf@gmx.de> (raw)
In-Reply-To: <87mueft8h5.fsf@web.de> (Michael Heerdegen's message of "Sat, 05 Oct 2019 19:20:22 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

Hi Michael,

>> Well, I haven't tested heavily. If you want, run your tests, and adapt
>> the text according to the results.
>
> What do you want to test - isn't it enough that some test cases don't
> work?  If it should work, that should be fixed.  If it doesn't have to
> work, what do we need to test?  If you don't know if it should work, I
> don't know how to find out.

I'm also short in time, and debbugs is not my primary concern. But so
what ...

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.

> I would prefer if you could care about it.  I have gotten removed two
> wisdom teeth (sorry if the verb is wrong), have a lot of other stuff to
> care about at the moment, and do know completely nothing about debbugs.
> I guess you can do it more efficiently and better.  It doesn't hurry.

I hope it will get better with your Weisheistszaehne! Wish you the best!

> Thanks,
>
> Michael.

Best regards, Michael.



  reply	other threads:[~2019-10-05 18:11 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 [this message]
2019-10-06 10:08                       ` Michael Heerdegen
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=87muefcbac.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.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).