From: Austin Clements <amdragon@MIT.EDU>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: add default value to notmuch-search-line-faces
Date: Tue, 31 Jan 2012 10:19:52 -0500 [thread overview]
Message-ID: <20120131151952.GC10898@mit.edu> (raw)
In-Reply-To: <87vcns10f1.fsf@nikula.org>
Quoth Jani Nikula on Jan 31 at 3:12 pm:
> On Thu, 26 Jan 2012 23:58:51 +0200, Jani Nikula <jani@nikula.org> wrote:
> > On Thu, 26 Jan 2012 14:41:46 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
> > > Quoth Jani Nikula on Jan 26 at 9:21 pm:
> > > > + ("flagged" :foreground "red"))
> > >
> > > Red is pretty universally used to indicate danger or a serious
> > > condition, while "flagged" is simply supposed to draw attention. I
> > > would say blue as a neutral and distinct indicator, but it also has
> > > poor visibility (I used to use blue, but found that when scanning my
> > > mail, I would habitually skip over flagged messages because they were
> > > dark, which was the opposite of what I wanted). Personally I've
> > > settled on yellow; it's visually distinct enough to be easily
> > > noticeable and bright enough that I don't skip over it, though it
> > > obviously wouldn't work on a light background.
> >
> > Can be yellow, I don't really care that much. But isn't a light
> > background the default for emacs in most distros? If that matters,
> > *shrug*.
>
> Ugh, yellow is absolutely horrible on a white background... that would
> certainly draw people to figure out how to change the settings. Now
> shall I send v2 with bold for unread and yellow for flagged, or can this
> go in as it is?
Sorry, I really meant to propose blue for flagged. The thing about
yellow was meant more as an aside. Blue is reasonably visible on both
light and dark backgrounds. It should draw people into customizing
it, while still being a reasonable default.
next prev parent reply other threads:[~2012-01-31 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 19:21 [PATCH] emacs: add default value to notmuch-search-line-faces Jani Nikula
2012-01-26 19:41 ` Austin Clements
2012-01-26 21:58 ` Jani Nikula
2012-01-31 13:12 ` Jani Nikula
2012-01-31 15:19 ` Austin Clements [this message]
2012-01-26 21:59 ` Jeremy Nickurak
2012-01-26 22:17 ` Austin Clements
2012-01-27 10:29 ` Mark Walters
2012-01-27 10:37 ` David Edmondson
2012-01-28 11:07 ` Mark Walters
2012-01-28 11:18 ` Mark Walters
2012-02-02 14:58 ` [PATCH v2] " Jani Nikula
2012-02-02 16:15 ` Tomi Ollila
2012-02-03 8:08 ` David Edmondson
2012-02-12 17:32 ` David Bremner
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=20120131151952.GC10898@mit.edu \
--to=amdragon@mit.edu \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/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).