Re: [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring

diff --git a/e6/4e00f3ddaf8f314bc3a9c820a407ffd15a6ffd b/e6/4e00f3ddaf8f314bc3a9c820a407ffd15a6ffd
new file mode 100644 (file)
index 0000000..7cf2876
--- /dev/null
+++ b/e6/4e00f3ddaf8f314bc3a9c820a407ffd15a6ffd
@@ -0,0 +1,110 @@
+Return-Path: <tomi.ollila@iki.fi>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 6D72A431FBD\r
+       for <notmuch@notmuchmail.org>; Sat,  8 Feb 2014 11:38:02 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id EpNPPKrIhPLg for <notmuch@notmuchmail.org>;\r
+       Sat,  8 Feb 2014 11:37:55 -0800 (PST)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+       by olra.theworths.org (Postfix) with ESMTP id 960F6431FBC\r
+       for <notmuch@notmuchmail.org>; Sat,  8 Feb 2014 11:37:55 -0800 (PST)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+       by guru.guru-group.fi (Postfix) with ESMTP id D1DF5100033;\r
+       Sat,  8 Feb 2014 21:37:43 +0200 (EET)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: "W. Trevor King" <wking@tremily.us>\r
+Subject: Re: [PATCH 00/17] nmbug-status: Python-3-compabitility and general\r
+       refactoring\r
+In-Reply-To: <20140208190923.GE14197@odin.tremily.us>\r
+References: <m2a9e6zppp.fsf@guru.guru-group.fi>\r
+       <20140204191453.GV14197@odin.tremily.us>\r
+       <m2fvnywsly.fsf@guru.guru-group.fi>\r
+       <m2fvnxvc2q.fsf@guru.guru-group.fi>\r
+       <20140205152738.GJ14197@odin.tremily.us>\r
+       <m28utp6ugv.fsf@guru.guru-group.fi>\r
+       <20140206181400.GP14197@odin.tremily.us>\r
+       <87ob2hogkr.fsf@zancas.localnet>\r
+       <20140208171617.GD14197@odin.tremily.us>\r
+       <m2eh3dsbje.fsf@guru.guru-group.fi>\r
+       <20140208190923.GE14197@odin.tremily.us>\r
+User-Agent: Notmuch/0.17+69~g761b031 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+       $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+       !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Sat, 08 Feb 2014 21:37:43 +0200\r
+Message-ID: <m27g95s8e0.fsf@guru.guru-group.fi>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 08 Feb 2014 19:38:02 -0000\r
+\r
+On Sat, Feb 08 2014, "W. Trevor King" <wking@tremily.us> wrote:\r
+\r
+> On Sat, Feb 08, 2014 at 08:29:41PM +0200, Tomi Ollila wrote:\r
+>> On Sat, Feb 08 2014, W. Trevor King wrote:\r
+>> > On Sat, Feb 08, 2014 at 09:54:28AM -0400, David Bremner wrote:\r
+>> >>=20\r
+>> >> yeah, the colour scheme is not my favourite. For the sake of being\r
+>> >> semi-constructive, I attach an alternative suggestion #ffd96e and\r
+>> >> #bce.\r
+>> >\r
+>> > Works for me.\r
+>>=20\r
+>> I'm fine with that too.\r
+>\r
+> Updated in my example and nmbug-status-python3 branch.\r
+>\r
+>> >> More importantly some of the threads are run together: e.g.=20\r
+>> >>=20\r
+>> >> id:"4eddf2b1.4288980a.0b74.5557@mx.google.com" and\r
+>> >> id:"E1RYMYd-0003wu-Ea@thinkbox.jade-hamburg.de"\r
+>> >\r
+>> > Both of those messages are part of the same thread\r
+>> > (thread:000000000000eaab on my box, but I doubt thread IDs are\r
+>> > portable), so I don't add a thread-separating space between them.\r
+>> > Would you like more message-separating space even between messages\r
+>> > in the same thread?\r
+>>=20\r
+>> =E2=80=A6\r
+>>=20\r
+>> I think the more space does not fix anything but it might help\r
+>> regognizing message boundaries a bit (and thus would be a nice\r
+>> feature).\r
+>\r
+> Added to my example and nmbug-status-python3 branch.  I'm using CSS\r
+> for this new spacing, so non-CSS browsers (e.g. w3m) won't render the\r
+> inter-message spacing.  I think the colored-link (second message row)\r
+> vs. default id (first message row) makes inter-message separation\r
+> clear enough in that case.\r
+\r
+The 2 0.5em:s adds up to 1em between messages and that IMHO makes the\r
+messages be too far apart from each other. I changed the padding-top\r
+and padding-bottom values to 0.25em which IMHO is better...\r
+\r
+> Cheers,\r
+> Trevor\r
+\r
+Tomi\r