From: Tassilo Horn <tassilo@member.fsf.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 7449@debbugs.gnu.org, Alex Harsanyi <AlexHarsanyi@gmail.com>
Subject: bug#7449: 24.0.50; Problems with the bug-querying mechanism
Date: Sat, 20 Nov 2010 18:02:05 +0100 [thread overview]
Message-ID: <87d3q0exo2.fsf@member.fsf.org> (raw)
In-Reply-To: <8739qw3thp.fsf@gmx.de> (Michael Albinus's message of "Sat, 20 Nov 2010 16:27:46 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi!
>>> . It seems not to support more than one keyword. E.g., if I type
>>> either "cursor" or "overlay", I get the bug #6687 listed in the
>>> results, but if I type "cursor overlay", I get an empty list. Did
>>> I understand the syntax of the keywords incorrectly? (Btw, it
>>> would be nice to tell the expected syntax in the prompt.)
>>
>> I totally agree, and I don't have any clue about the syntax, too. It's
>> the same that you would use in the search-by-subject field in the web
>> interface.
>
> I have in mind a simple interface. Strings, separated by spaces, are
> used as AND concatenation.
That's what I've expected from the normal search, too. And it seems to
be just that, but with the major annoyance of recognizing a subject like
next-line, no worky!
as words "next-line,", "no", and "worky!". So you'll find the bug with
keyword "no", but not with "next-line", because the comma is missing...
Bye,
Tassilo
next prev parent reply other threads:[~2010-11-20 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1290257071.20963.bug-gnu-emacs@gnu.org>
2010-11-20 14:19 ` bug#7449: 24.0.50; Problems with the bug-querying mechanism Tassilo Horn
2010-11-20 15:27 ` Michael Albinus
2010-11-20 17:02 ` Tassilo Horn [this message]
2010-11-20 12:29 ` Eli Zaretskii
2010-11-23 19:44 ` Glenn Morris
2010-11-24 12:21 ` Alex Harsanyi
2012-11-08 0:20 ` Glenn Morris
2012-11-08 7:29 ` Tassilo Horn
2012-11-10 23:20 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3q0exo2.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=7449@debbugs.gnu.org \
--cc=AlexHarsanyi@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.