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
Date: Sat, 03 Jun 2023 00:49:34 -0400 [thread overview]
Message-ID: <87fs79up41.fsf@kyleam.com> (raw)
In-Reply-To: <87o7lyi1gc.fsf@fsfe.org>
Jelle Licht writes:
> As mentioned, I use debbugs.el to interact with the issue tracker. [1]
> [...]
> [1]: Not entirely relevant to the issue at hand, but I also have all
> guix-patches messages available and indexed in my local notmuch
> setup. [...]
Because you have the local Notmuch store, perhaps you'd be interested in
debbugs.el visiting the message in Notmuch rather than Gnus. As I said,
I haven't actually used debbugs.el much, but I stumbled on this in my
config:
;; Modified from function in Nicolas Petton's emacs configuration
;; (https://gitlab.petton.fr/nico/emacs.d/, 208407f53a)
(defun km/debbugs-notmuch-select-report (&rest _)
(require 'debbugs-gnu)
(let* ((status (debbugs-gnu-current-status))
(id (cdr (assq 'id status)))
(merged (cdr (assq 'mergedwith status))))
(setq merged (if (listp merged) merged (list merged)))
(unless id
(user-error "No bug report on the current line"))
(let ((address (format "%s@debbugs.gnu.org" id))
(merged-addresses (string-join (mapcar (lambda (id)
(format "%s@debbugs.gnu.org" id))
merged)
" ")))
(notmuch-tree (format "%s %s" address merged-addresses)))))
(advice-add 'debbugs-gnu-select-report :override
#'km/debbugs-notmuch-select-report)
prev parent reply other threads:[~2023-06-03 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 14:12 On the road to (GNU) debbugs support, some blockers Jelle Licht
2023-05-31 4:05 ` Kyle Meyer
2023-06-02 10:49 ` Jelle Licht
2023-06-03 2:34 ` Kyle Meyer
2023-06-03 5:34 ` Kyle Meyer
2023-06-03 4:49 ` Kyle Meyer [this message]
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://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs79up41.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=jlicht@fsfe.org \
--cc=piem@inbox.kyleam.com \
/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.kyleam.com/piem/
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).