unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Tassilo Horn <tassilo@member.fsf.org>
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 16:27:46 +0100	[thread overview]
Message-ID: <8739qw3thp.fsf@gmx.de> (raw)
In-Reply-To: <87hbfcf56c.fsf@member.fsf.org> (Tassilo Horn's message of "Sat,  20 Nov 2010 15:19:55 +0100")

Tassilo Horn <tassilo@member.fsf.org> writes:

> Hi Eli,

Hi,

>> The new feature for querying existing bugs is nice (thanks!), but it
>> needs some polishing, IMO:
>
> Definitively.  I've just gotten a mail from Michael Albinus.  He's
> trying to implement a proper debbugs interface using its SOAP protocol
> with far more capabilities than what I've hacked up.  So probably many
> of your remarks may be already addressed in his works.
>
> With these new information, I think that it's seems a good idea to wait
> for his implementation and then use that for all the querying and result
> parsing stuff.

There are (at least) 2 problems which might delay publishing a little bit:

- The SOAP interface does not support querying bug subjects yet. I'm
  investigating, whether this could be enhanced.

- My code uses soap-client.el from
  <http://code.google.com/p/emacs-soap-client/>. I've asked Alex
  Harsanyi, the author, for signing FSF legal papers, and he agreed. So
  we must wait, until this procedure is finished.

>>  . It doesn't seem to handle non-ASCII (e.g., UTF-8) characters well.
>>    E.g., I get octal escapes in the description of bug#7373.
>
> Yep, it's totally agnostic to url-encoding, except that it replaces
> spaces in the keywords with + when querying.

It shouldn't be a problems when handled via SOAP.

>>  . 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. For the time being this could be in the bug's
subject, but I would also like to have a full text search in the
future. If the search is directed to other bug attributes, it could be
prefixed by the attribute, like "package:gnus" or
"submitter:tassilo@member.fsf.org".

> Bye,
> Tassilo

Best regards, Michael.





  reply	other threads:[~2010-11-20 15:27 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 [this message]
2010-11-20 17:02     ` Tassilo Horn
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

  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=8739qw3thp.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=7449@debbugs.gnu.org \
    --cc=AlexHarsanyi@gmail.com \
    --cc=tassilo@member.fsf.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).