Date: Sat, 8 Feb 2014 11:09:23 -0800
From: "W. Trevor King" <wking@tremily.us>
To: Tomi Ollila <tomi.ollila@iki.fi>
Subject: Re: [PATCH 00/17] nmbug-status: Python-3-compabitility and general
	refactoring
Message-ID: <20140208190923.GE14197@odin.tremily.us>
References: <m2a9e6zppp.fsf@guru.guru-group.fi>
	<20140204191453.GV14197@odin.tremily.us>
	<m2fvnywsly.fsf@guru.guru-group.fi>
	<m2fvnxvc2q.fsf@guru.guru-group.fi>
	<20140205152738.GJ14197@odin.tremily.us>
	<m28utp6ugv.fsf@guru.guru-group.fi>
	<20140206181400.GP14197@odin.tremily.us>
	<87ob2hogkr.fsf@zancas.localnet>
	<20140208171617.GD14197@odin.tremily.us>
	<m2eh3dsbje.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FlUFLWgqFf7wS8YX"
Content-Disposition: inline
In-Reply-To: <m2eh3dsbje.fsf@guru.guru-group.fi>
OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;
	url=http://tremily.us/pubkey.txt
User-Agent: Mutt/1.5.22 (2013-10-16)
Cc: notmuch@notmuchmail.org
Precedence: list


--FlUFLWgqFf7wS8YX
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 08, 2014 at 08:29:41PM +0200, Tomi Ollila wrote:
> On Sat, Feb 08 2014, W. Trevor King wrote:
> > On Sat, Feb 08, 2014 at 09:54:28AM -0400, David Bremner wrote:
> >> W. Trevor King writes:
> >> > I'll remove this once the series lands, but I've currently got a
> >> > preview up at http://tremily.us/status.html
> >>=20
> >> yeah, the colour scheme is not my favourite. For the sake of being
> >> semi-constructive, I attach an alternative suggestion #ffd96e and
> >> #bce.
> >
> > Works for me.
>=20
> I'm fine with that too.

Updated in my example and nmbug-status-python3 branch.

> >> More importantly some of the threads are run together: e.g.=20
> >>=20
> >> id:"4eddf2b1.4288980a.0b74.5557@mx.google.com" and
> >> id:"E1RYMYd-0003wu-Ea@thinkbox.jade-hamburg.de"
> >
> > Both of those messages are part of the same thread
> > (thread:000000000000eaab on my box, but I doubt thread IDs are
> > portable), so I don't add a thread-separating space between them.
> > Would you like more message-separating space even between messages
> > in the same thread?
>=20
> =E2=80=A6
>=20
> I think the more space does not fix anything but it might help
> regognizing message boundaries a bit (and thus would be a nice
> feature).

Added to my example and nmbug-status-python3 branch.  I'm using CSS
for this new spacing, so non-CSS browsers (e.g. w3m) won't render the
inter-message spacing.  I think the colored-link (second message row)
vs. default id (first message row) makes inter-message separation
clear enough in that case.

Cheers,
Trevor

--=20
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--FlUFLWgqFf7wS8YX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJS9oDgAAoJEKKfehoaNkbto18P/ienItlfn+oX7ZJxi3Zlsk1c
RbYYEFqJsgoLUwSelamxFRxB4jQhPLZJCqt2zSLdTXKw54kxpa7EEKdoyboRiO7z
x8jdgNzK+Zb+Uc3Rhr6hSXxe2psK0AlWfudKt6RQA5hOLwzV4v57EZ3kXEt+lp4U
00OKWY9XBs//mYQTVCrLQEjHzvjWskDZvr0hIa26cvhS0XaUmPWXyDxq6ZNFL+Ko
j0JtLp+Sbw/Fw5zP6ZXpaPjZyF6ePSU2TkTHmxo8u19Cfg0DOJMSBIlItPLBuYgb
kw6ceOBe3PqWRxMlMOXFsezp2egFeZ/OzhW9JiABtZIMbx91fbh24rfzPVMlGMIV
6fd/V+7mrB8HlOvQ1cRl3EeZugaZHs/W5kyhlcM2dmd8m/LSXSVgiYGTu4BuEwLO
OJ4VXrQJjp8EEWE1x6ca+gYJicXwIkcQi+J1fbNSD1WZXeyqPmjHGCdLo1BHYx/Z
xjVzO9qr6X2BEhMJ52Qoy8ZnnFAciS8OMZ5P5QmI66QsILwZNwYN0FZWZhsstATR
zuedcSfBSJIA1hYIFHDSYymN5jpOlSOjevmAdNOFavS2RkxlafSqoiLJMyjM0qtn
RDly8CogffDR8Z6rmFp61cqWT1wq5g7DN25vh+ZWTyU6bbjz5UrasxYEEU+KBQPN
QyRjnXr49qDekbWVZb80
=0oJW
-----END PGP SIGNATURE-----

--FlUFLWgqFf7wS8YX--