From: "W. Trevor King" <wking@tremily.us>
To: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring
Date: Thu, 6 Feb 2014 10:14:01 -0800 [thread overview]
Message-ID: <20140206181400.GP14197@odin.tremily.us> (raw)
In-Reply-To: <m28utp6ugv.fsf@guru.guru-group.fi>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On Thu, Feb 06, 2014 at 12:54:56AM +0200, Tomi Ollila wrote:
> On Wed, Feb 05 2014, "W. Trevor King" wrote:
> > On Wed, Feb 05, 2014 at 05:00:45PM +0200, Tomi Ollila wrote:
> >> #DFF for the light-blue works better for me.
> >
> > I'm fine with that. As I said in my cover letter, I'm happy to have
> > alternative color schemes suggested. Does anyone else want to chime
> > in on better defaults? This should probably also be configurable via
> > status-config.json. Maybe:
> >
> > { "style": {"html": {"thread-colors": ["#DFF", "#FEF"]}}}
>
> Maybe we can persuade David to test-run new notmuch-status in
> his production server before it is pushed to notmuch master, and
> bikeshed the style in http://nmbug.tethera.net/status/
I'll remove this once the series lands, but I've currently got a
preview up at http://tremily.us/status.html
> probably no-one is interested to configure those later (if we even
> get bikeshed comments... ;)
I suppose we can revisit this when someone with an existing color
scheme decides to use nmbug and nmbug-status as their bugtracker (red
a gray for Red Hat? Blue and yellow for Python? ;). Until then, I'm
fine with hardcoding this.
Cheers,
Trevor
--
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-06 18:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 10:59 [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring W. Trevor King
2014-02-03 10:59 ` [PATCH 01/17] nmbug-status: Convert to Python-3-compatible print functions W. Trevor King
2014-02-03 10:59 ` [PATCH 02/17] nmbug-status: Use email.utils instead of rfc822 W. Trevor King
2014-02-03 10:59 ` [PATCH 03/17] nmbug-status: Decode Popen output using the user's locale W. Trevor King
2014-02-03 10:59 ` [PATCH 04/17] nmbug-status: Factor config-loading out into read_config W. Trevor King
2014-02-03 10:59 ` [PATCH 05/17] nmbug-status: Add metavars for --config and --get-query W. Trevor King
2014-02-03 10:59 ` [PATCH 06/17] nmbug-status: Consolidate functions and main code W. Trevor King
2014-02-03 10:59 ` [PATCH 07/17] nmbug-status: Don't require write access W. Trevor King
2014-02-03 10:59 ` [PATCH 08/17] nmbug-status: Consolidate HTML header printing W. Trevor King
2014-02-03 10:59 ` [PATCH 09/17] nmbug-status: Add a Python-3-compatible urllib.parse.quote import W. Trevor King
2014-02-03 10:59 ` [PATCH 10/17] nmbug-status: Add Page and HtmlPage for modular rendering W. Trevor King
2014-02-03 10:59 ` [PATCH 11/17] nmbug-status: Normalize table HTML indentation W. Trevor King
2014-02-03 10:59 ` [PATCH 12/17] nmbug-status: Convert from XHTML 1.0 to HTML 5 W. Trevor King
2014-02-03 10:59 ` [PATCH 13/17] nmbug-status: Encode output using the user's locale W. Trevor King
2014-02-03 10:59 ` [PATCH 14/17] nmbug-status: Anchor with h3 ids instead of a names W. Trevor King
2014-02-03 10:59 ` [PATCH 15/17] nmbug-status: Quote the title when using it as an id W. Trevor King
2014-02-08 23:18 ` W. Trevor King
2014-02-09 9:34 ` Tomi Ollila
2014-02-03 10:59 ` [PATCH 16/17] nmbug-status: Use <code> and <p> markup where appropriate W. Trevor King
2014-02-03 10:59 ` [PATCH 17/17] nmbug-status: Color threads in HTML output W. Trevor King
2014-02-03 21:10 ` [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring Tomi Ollila
2014-02-04 0:53 ` W. Trevor King
2014-02-04 10:30 ` Tomi Ollila
2014-02-04 13:07 ` David Bremner
2014-02-04 15:50 ` W. Trevor King
2014-02-04 17:39 ` W. Trevor King
2014-02-04 16:11 ` W. Trevor King
2014-02-04 18:40 ` Tomi Ollila
2014-02-04 19:14 ` W. Trevor King
2014-02-04 20:06 ` Tomi Ollila
2014-02-05 15:00 ` Tomi Ollila
2014-02-05 15:24 ` Tomi Ollila
2014-02-05 15:31 ` W. Trevor King
2014-02-07 22:15 ` W. Trevor King
2014-02-05 15:27 ` W. Trevor King
2014-02-05 22:54 ` Tomi Ollila
2014-02-06 18:14 ` W. Trevor King [this message]
2014-02-08 16:11 ` David Bremner
[not found] ` <87ob2hogkr.fsf@zancas.localnet>
2014-02-08 17:16 ` W. Trevor King
2014-02-08 18:29 ` Tomi Ollila
2014-02-08 19:09 ` W. Trevor King
2014-02-08 19:37 ` Tomi Ollila
2014-02-08 22:19 ` W. Trevor King
2014-02-04 17:48 ` W. Trevor King
2014-02-04 18:34 ` Tomi Ollila
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140206181400.GP14197@odin.tremily.us \
--to=wking@tremily.us \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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://yhetil.org/notmuch.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).