From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kyle@kyleam.com>
Received: from mp12.migadu.com ([2001:41d0:203:375::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by ms12.migadu.com with LMTPS
	id ySnMDfHQemRbYQAATFOONw
	(envelope-from <kyle@kyleam.com>)
	for <larch@inbox.kyleam.com>; Sat, 03 Jun 2023 07:34:41 +0200
Received: from mta1.migadu.com ([2001:41d0:203:375::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by mp12.migadu.com with LMTPS
	id mBrhDPHQemQpXAEAauVa8A
	(envelope-from <kyle@kyleam.com>)
	for <larch@inbox.kyleam.com>; Sat, 03 Jun 2023 07:34:41 +0200
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1;
	t=1685770481;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=jKb+p1Wp5IDm6XaMhx7/RWyyDG5TGIKWW0row3xnJpg=;
	b=G4OQ7SCe/xSihQy7rHrQKSLXld0mErTRRlEoSeySWEhVqpzRObiqVUG/UOMMXt6chkLZUN
	gB8f8fdYEXieGovfq21XWNhilofHsxsJx2pyqa1vZNSKnPm6MMKQpwxOjjKLaWFldmw1W9
	0SspODbCjMRoMaQyZ11iISYFHD5uHBqNZky+JfIb8XW1WwWmwpYW0jGktz4GEVsojeG5ct
	g5wOk4am9vKxk7Wn9aGyrhgPOMlqM0s/6H08cYMlFrMtKChBFyBXXAEBUtJwDuQaSTjmTG
	eRBc+/6WWBiEeDKMKJrEnK4/wGDD/UX4rEyAP1IwCCqJfSpPA9pjrHerU+Oamw==
From: Kyle Meyer <kyle@kyleam.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: piem@inbox.kyleam.com
Subject: Re: On the road to (GNU) debbugs support, some blockers
In-Reply-To: <87y1l1e0ju.fsf@kyleam.com>
References: <87y1l9ualg.fsf@fsfe.org> <87zg5l16yq.fsf@kyleam.com>
 <87o7lyi1gc.fsf@fsfe.org> <87y1l1e0ju.fsf@kyleam.com>
Date: Sat, 03 Jun 2023 01:34:37 -0400
Message-ID: <87cz2dun0y.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Migadu-Flow: FLOW_OUT
X-TUID: 7CVHl0qEnfvP

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.