Re: On the road to (GNU) debbugs support, some blockers

[Kyle Meyer <kyle@kyleam.com>]

Kyle Meyer writes:

> I'll look into debbugs.el a bit more because I don't have a good
> understanding of where it's getting the messages from and how it's
> interacting with Gnus, but it sounds like the X-GNU-PR-Package header is
> the way to go for debbugs.el support.

debbugs-gnu-select-report (which has built-in support for Gnus or Rmail)
is getting the mbox from

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=%s;mboxmaint=yes

So indeed

 * piem-gnus-mid-to-thread should make sure the input isn't already an
   mbox before inserting the From_ line

 * X-GNU-PR-Package looks like the best (or really only) option to
   connect an mbox from debbugs.gnu.org to an inbox

> I'm curious whether it will make sense to have a custom integration
> library, perhaps one that builds on top of piem-gnus, but perhaps that
> will be clearer once I take a closer look.

In most cases, users will probably be calling piem after selecting the
issue and entering Gnus/Rmail or, if they override the selection
mechanism, perhaps Notmuch (or even lei :>).  So support mostly just
comes from those libraries.

However, I do think it'd be nice to add an integration library for the
Debbugs mode buffer.  With

  (debbugs-gnu-current-status)

we can get the package and message ID, so it'd be straightforward to
define a piem-debbugs-get-inbox and piem-debbugs-get-mid.