From: Ricardo Wurmus <rekado@elephly.net>
To: Jack Hill <jackhill@jackhill.us>
Cc: guix-devel@gnu.org
Subject: Re: Mumi now uses raw emails and Mu
Date: Tue, 23 Jul 2019 13:01:58 +0200 [thread overview]
Message-ID: <875zntc8ux.fsf@elephly.net> (raw)
In-Reply-To: <87blxme6pk.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Forking Mu requires a rough understanding how it currently works.
> Obviously, it must parse emails and extract certain headers. We only
> need it to extract a few more headers such as “X-Debbugs-Envelope-To”,
> which contains the Debbugs bug number. (I don’t know if that header is
> set for *all* emails that end up in the bug tracker, but that’s
> something we have to figure out.)
>
> Mu is written in C and the header extraction probably happens in the C
> code as well.
I forked Mu and let it store the “X-Debbugs-Envelope-To” header in the
database:
https://git.elephly.net/?p=software/mumimu.git;a=shortlog;h=refs/heads/mumimu
The “bugid” query can be used to quickly retrieve messages belonging to
a certain Debbugs bug, so something like this will print the message
subject for all messages relating to bug 31023.
(use-modules (mumimu))
(mu:initialize (%config 'mail-dir))
(for-each
(lambda (msg)
(pk (mu:subject msg)))
(mu:message-list "bugid:31023"))
This seems to actually work. Still don’t know if all emails actually
have that header; if they don’t we’ll need to implement an alternative
way to get the bug number in “get_bugid” (lib/mu-msg-file.c).
--
Ricardo
next prev parent reply other threads:[~2019-07-23 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 20:18 Mumi now uses raw emails and Mu Ricardo Wurmus
2019-07-22 0:41 ` Jack Hill
2019-07-22 9:53 ` Ricardo Wurmus
2019-07-23 11:01 ` Ricardo Wurmus [this message]
2019-07-23 13:49 ` Ricardo Wurmus
2019-07-24 17:07 ` Arun Isaac
2019-07-24 17:45 ` Ricardo Wurmus
2019-07-24 18:46 ` Arun Isaac
2019-07-22 17:54 ` Arun Isaac
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zntc8ux.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=jackhill@jackhill.us \
/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.savannah.gnu.org/cgit/guix.git
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).