From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: https://issues.guix.info Date: Tue, 04 Sep 2018 02:33:18 +0200 Message-ID: <87d0tuyucx.fsf@elephly.net> References: <878t4l0xsz.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58446) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fwzI3-0005em-11 for guix-devel@gnu.org; Mon, 03 Sep 2018 20:33:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fwzHz-0004lm-TV for guix-devel@gnu.org; Mon, 03 Sep 2018 20:33:55 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21049) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fwzHz-0004fs-Hh for guix-devel@gnu.org; Mon, 03 Sep 2018 20:33:51 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Arun Isaac Cc: guix-devel@gnu.org Hi Arun, >> - proper handling of attachments in multipart messages. If a multipart >> message contains an attachment, mumi tries to display it like any >> other multipart type. > > Is this about allowing attached patches to be downloaded? Is it > currently possible to download patches using mumi? It would be nice to > use mumi for my entire workflow, and not have to fallback to the old > debbugs web interface. This is now possible. I currently only decode attachments that are in base64 and quoted printable formats; all others are sent as is. > Also, is there any value in having a pure guile email parser instead of > using bindings to mailutils? I attempted a similar project, and for some > reason, I ended up writing an email parser from scratch using (ice-9 > peg). But, now that I see how you have used mailutils bindings, I am > unsure if writing an email parser from scratch was wise. However, if you > think it is worthwhile, I can contribute that code to mumi. I=E2=80=99m not using a lot of mailutils. I use the following procedures: - mu-address-get-email - mu-address-get-personal (problem: swallows non-ASCII characters) - mu-header-decode - mu-decoder-port Of all these only =E2=80=9Cmu-decoder-port=E2=80=9D would be non-trivial to= implement. It=E2=80=99s used to decode strings that are encoded as =E2=80=9Cquoted-pri= ntable=E2=80=9D. It wouldn=E2=80=99t be too difficult to implement in pure Guile =E2=80=93 I ju= st wanted to save time. I=E2=80=99d be happy if your work on email parsers could end up in mumi and replace some of my own poor quality code :) -- Ricardo