From: "Evgeny M. Zubok" <evgeny.zubok@tochka.ru>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: debbugs.el
Date: Fri, 25 Feb 2011 02:44:36 +0300 [thread overview]
Message-ID: <877hcpknff.fsf@tochka.ru> (raw)
In-Reply-To: <87vd093bwn.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
> That was my motivation writing debbugs.el. I've also started an nnir
> integration, but I failed badly due to missing gnus knowledge.
There is debian-el package in Debian repository. It is also the suitable
place to push debbugs.el into. debian-el has a number of useful
features: you can file a bug with (debian-bug), fill the tags in the
mail body, compose control messages for control@bugs.debian.org
(debian-bts-control), download mbox with log of selected bug number,
view this mbox in Gnus as a tree (debian-bug-get-bug-as-email), reply to
someone.
> OTOH, the debbugs SOAP interface is poor, there are only very basic
> information one could retrieve, and there is no "activiation" function
> (changing whatever for a bug). So it might be better, we first make a
> prototype implementation integrating it with nnir etc, before adding it
> to Emacs core. For this purpose, it might be sufficient to bring it to
> elpa (or gnus) for a while.
I made an attempt to create Emacs interface to Debbugs/SOAP year
ago. I've wrote a simple SOAP client library in Emacs Lisp. By using
this library my debbugs-mode requested for a bug list (filtered by
different parameters: package, severity, tags, etc.) along with the
status information for every bug. Bug reports are grouped by severity,
sorted by bug number and displayed in outline-mode (folding/unfolding
out of a box).
One year old screenshot:
http://s006.radikal.ru/i214/1001/d1/08ef5f85246e.png
I didn't use the SOAP to request the bug logs because Debbugs/SOAP won't
send the attachments. When I hit RET against the bug entry, the
maintainer's mbox for selected bug is downloaded. mbox can be opened
either in Gnus or in RMAIL. I used the latter to be neutral to the users
of different mail programs: Gnus, Wunderlust, etc. Any message from the
log can be replied with your favourite mail program (Gnus in my case).
My work can be viewed as early technical preview; it has many dirty
hacks (hardcoded XML namespaces in SOAP client library is the most
simple example), bugs. The code is ugly, I was in hurry to make the mode
work. That's because it's not published yet. :)
I want to start hacking again and hope to finish it some day. :)
next prev parent reply other threads:[~2011-02-24 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8762sa9770.fsf@gmx.de>
[not found] ` <87pqqibr30.fsf@stupidchicken.com>
[not found] ` <87mxllambw.fsf@marauder.physik.uni-ulm.de>
2011-02-24 11:33 ` debbugs.el Michael Albinus
2011-02-24 23:44 ` Evgeny M. Zubok [this message]
2011-02-25 10:55 ` debbugs.el Michael Albinus
2011-02-25 16:51 ` debbugs.el Evgeny M. Zubok
2011-03-01 10:15 ` debbugs.el Michael Albinus
2011-03-02 15:56 ` debbugs.el Evgeny M. Zubok
2011-02-25 3:37 ` debbugs.el Lars Ingebrigtsen
2011-02-25 8:17 ` debbugs.el Eli Zaretskii
2011-02-25 8:33 ` debbugs.el Michael Albinus
2011-02-25 8:54 ` debbugs.el Eli Zaretskii
2011-02-25 9:29 ` debbugs.el Miles Bader
2011-02-25 9:55 ` debbugs.el Eli Zaretskii
2011-02-25 15:43 ` debbugs.el Stefan Monnier
2011-02-25 15:52 ` debbugs.el Eli Zaretskii
2011-02-25 9:59 ` debbugs.el Lars Ingebrigtsen
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=877hcpknff.fsf@tochka.ru \
--to=evgeny.zubok@tochka.ru \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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.
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 NNTP newsgroup(s).