[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Mummi wishlist: API using Message-ID

From: zimoun
Subject: Mummi wishlist: API using Message-ID
Date: Thu, 17 Sep 2020 01:51:01 +0200


Today <> is really useful and IMHO better than the
classic Debbugs interface [1].

Bug reports (and patches) are still sent by email, the core of the
Debbugs bug tracker.  However, Mummi does not use the unique identifier
Message-ID as address, AFAICT.  Therefore, it can be tricky to link
between my emails reader/writer and the web interface.

Let take an example.  From my typical use case. :-)

My subscription to bug-guix (or guix-patches) sends me emails and I read
them with emacs-notmuch (but it is not Emacs related, since any good
email reader seems able to do the same).

When I want to refer to one specific message, I have to open my web
browser and go to <> then scroll a bit to find
the relevant message, click to the date to get the associated number,
copy the URL and go back to my email writer and finally paste the link.

For example <>.  The number #16 is
really difficult to guess. :-)

Instead, it is easy to get the Message-ID.  (Using emacs-notmuch, only
hit the key ’ci’) Therefore, it could be nice to be able to provide
e.g., the URL:


redirecting to <>.  And maybe the
current webpage could provide the Message-ID, easy to copy and then
paste in my email reader.

Another (Emacs related) example is emacs-debbugs.
  C-u M-x debbugs-gnu RET guix RET n y
  M-x debbugs-gnu-bugs RET 33899 RET RET
  Read messages

Well, in the relevant message, I run “M-x debbugs->url” and get the
ready-to-be-pasted URL:


with the naive Emacs function:

--8<---------------cut here---------------start------------->8---
(defun debbugs->url ()
  (let ((url "";)
    (with-current-buffer gnus-article-buffer
      (gnus-summary-toggle-header 1)
      (setq mid (message-fetch-field "Message-ID"))
      (gnus-summary-toggle-header -1))
    (while (string-match "[<>]" mid)
      (setq mid (replace-match "" t t mid)))
    (kill-new (concat url mid))
    (message mid)))
--8<---------------cut here---------------end--------------->8---

Last and off-topic to the Subject :-), the tool ’public-inbox’ exposes
such API and then it seems easier to refer to relevant message than
going by hand on e.g. <>
to find it.

An unofficial (but almost? serving org-mode list [2]) example is
demonstrated here:


Does it make to sense to have something similar,
e.g. <> serving the ’public-inbox’?

[2] <>

All the best,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]