From: Lennart Borgman <lennart.borgman@gmail.com>
To: "K. Richard Pixley" <rich@noir.com>
Cc: bug-gnu-emacs@gnu.org
Subject: bug#7771: 23.1; can't turn off font-lock-mode globally
Date: Mon, 3 Jan 2011 23:04:36 +0100 [thread overview]
Message-ID: <AANLkTik66tUu_DfTy=oZwTzMzQ1-h1BYFSfsszfC_qWp@mail.gmail.com> (raw)
In-Reply-To: <4D224008.3080503@noir.com>
On Mon, Jan 3, 2011 at 10:30 PM, K. Richard Pixley <rich@noir.com> wrote:
> On 20110103 13:02, Lennart Borgman wrote:
>>
> I have no complaint or problem with dimmed or bolded. Dimmed certainly
> could become illegible if it were sufficiently dim, but it seems to be fine
> in most cases. Unlike, say, dim yellow text on off white background which
> is essentially invisible. Or red on green background or yellow on blue, (or
> vice verse), which are completely invisible.
>
> Most programmers aren't color experts. They just slap up what seem like
> contrasting colors to them without much thought to subjective experience,
> (color blindness, cognitive variance, environmental factors like X11
> themeing), color set themeing, look-and-feel coordination, pleasing
> presentation, etc.
>
> Thunderbird uses color and I find their use of color constructive.
>
> It's low/no contrast color and "bad" use of color to which I object, (and
> 95% of color uses are "bad", ime).
>
> I want the "bad" color to go away. And that seems to be primarily font-lock
> uses.
Then perhaps the best solution would rather be a color theme adjusted
to your needs? I mean in case that is possible to figure out on a more
general level. Since you say that thunderbird seems to have done that
it looks possible to me.
next prev parent reply other threads:[~2011-01-03 22:04 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 19:17 bug#7771: 23.1; can't turn off font-lock-mode globally K. Richard Pixley
2011-01-02 22:56 ` Leo
2011-01-02 23:19 ` K. Richard Pixley
2011-01-03 8:48 ` Leo
2011-01-02 23:49 ` Stefan Monnier
2011-01-03 0:27 ` K. Richard Pixley
2011-01-03 3:55 ` Stefan Monnier
2011-01-03 5:57 ` Glenn Morris
2011-01-03 6:00 ` Glenn Morris
[not found] ` <mailman.4.1294035825.27854.bug-gnu-emacs@gnu.org>
2011-01-03 6:56 ` K. Richard Pixley
2011-01-03 8:13 ` Drew Adams
2011-01-03 16:42 ` Lennart Borgman
2011-01-03 17:29 ` Drew Adams
2011-01-03 17:32 ` Lennart Borgman
2011-01-03 17:40 ` Drew Adams
[not found] ` <mailman.1.1294073635.27149.bug-gnu-emacs@gnu.org>
2011-01-03 18:40 ` K. Richard Pixley
2011-01-03 19:52 ` Eli Zaretskii
2011-01-03 20:29 ` K. Richard Pixley
2011-01-03 20:39 ` Eli Zaretskii
2011-01-03 21:02 ` Lennart Borgman
2011-01-03 21:30 ` K. Richard Pixley
2011-01-03 22:04 ` Lennart Borgman [this message]
2011-01-03 22:14 ` K. Richard Pixley
[not found] ` <mailman.3.1294088031.614.bug-gnu-emacs@gnu.org>
2011-01-03 22:27 ` K. Richard Pixley
[not found] ` <mailman.1.1294028628.27854.bug-gnu-emacs@gnu.org>
2011-01-03 22:23 ` K. Richard Pixley
2011-01-04 4:05 ` Eli Zaretskii
2011-01-04 4:21 ` K. Richard Pixley
2011-01-03 0:29 ` K. Richard Pixley
2011-01-03 1:55 ` Glenn Morris
2011-01-03 3:21 ` Lennart Borgman
2011-01-03 13:04 ` Eli Zaretskii
[not found] ` <mailman.30.1294025024.15403.bug-gnu-emacs@gnu.org>
2011-01-03 4:10 ` K. Richard Pixley
2011-01-03 5:34 ` Stefan Monnier
2011-01-03 6:52 ` K. Richard Pixley
2011-01-03 8:13 ` Drew Adams
2011-01-03 13:43 ` Eli Zaretskii
2011-01-03 16:00 ` Drew Adams
2011-01-03 18:01 ` Eli Zaretskii
2011-01-03 18:09 ` Drew Adams
2011-01-03 18:26 ` Eli Zaretskii
[not found] ` <mailman.1.1294062865.25287.bug-gnu-emacs@gnu.org>
2011-01-03 18:38 ` K. Richard Pixley
[not found] ` <mailman.10.1294043026.27854.bug-gnu-emacs@gnu.org>
2011-01-03 18:33 ` K. Richard Pixley
[not found] ` <mailman.22.1294021456.15403.bug-gnu-emacs@gnu.org>
2011-01-03 4:14 ` K. Richard Pixley
2011-01-03 0:31 ` K. Richard Pixley
2011-01-03 1:20 ` K. Richard Pixley
2011-01-03 1:54 ` Glenn Morris
2011-01-03 2:08 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTik66tUu_DfTy=oZwTzMzQ1-h1BYFSfsszfC_qWp@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=rich@noir.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.