From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Minor colouring (font lock) annoyance
Date: Fri, 24 Apr 2009 14:29:39 -0400 [thread overview]
Message-ID: <877i19sy5o.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <D792C05C-29E6-4EB3-9FD9-26D0112BE197@gmail.com> (Carsten Dominik's message of "Fri\, 24 Apr 2009 20\:22\:52 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Apr 24, 2009, at 8:20 PM, Bernt Hansen wrote:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> I do not actively color these tasks, but any headlines that
>>> have been *visible* in a window will have been fontified,
>>> others will not have bee fontified. Org just copies the
>>> text for this list. Maybe I should make then all without
>>> colors?
>>
>> Okay. That's a perfect explanation for me -- and I'll just ignore
>> that
>> color or lack of colour issue. It's actually a lot easier to read
>> coloured than not so please don't bother making them all black. :)
>
> I can also actively give them a color. Should these be the correct
> level colors, or some particular color?
The actual level colours with highlighted TODO keywords and other
cookies would be ideal I think.
I find the TODO keywords and cookies in a different font from the
heading text helps a lot. Also if different tasks are at different
levels they get different heading text colours which breaks up the list
nicely.
-Bernt
next prev parent reply other threads:[~2009-04-24 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 17:53 Minor colouring (font lock) annoyance Bernt Hansen
2009-04-24 18:18 ` Carsten Dominik
2009-04-24 18:20 ` Bernt Hansen
2009-04-24 18:22 ` Carsten Dominik
2009-04-24 18:29 ` Bernt Hansen [this message]
2009-05-05 8:33 ` Carsten Dominik
2009-05-05 12:21 ` Bernt Hansen
2009-05-05 12:45 ` Carsten Dominik
2009-05-05 12:49 ` Bernt Hansen
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877i19sy5o.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).