emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Capitalisation and good taste ?
Date: Wed, 11 Jan 2012 08:49:44 +0100	[thread overview]
Message-ID: <80hb02znjb.fsf@somewhere.org> (raw)
In-Reply-To: 87pqerfh0h.fsf@iro.umontreal.ca

Hi Bastien,

François Pinard wrote:
> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>> Eric Schulte <eric.schulte-KK0ffGbhmjU@public.gmane.org> writes:
>
>>> That said I'm happy that Org-mode is forgiving enough to allow me to
>>> lowercase most of my keywords locally.
>
>> Actually, I'm thinking of another solution:
>
>> - keep one-line option/environment keywords uppercase
>>   #+NAME
>>   #+HTML
>>   #+TITLE
>>   #+...
>
>> - use lowercase for multi-lines environments keywords
>>   #+begin_ascii
>>   #+begin_html
>>   #+results
>
>> This is the only good criterium I can think of, and that
>> way people using easy templates will not be surprised to
>> see #+begin_xxx in the manual.
>
> I surely like this! :-).

So do I.

> Could the highlighting be made consistent as well?  I would suggest that
> gray is uniformly kept for all one-line option/environment keywords.
> Currently, #+TITLE is gray, #+OPTIONS is red, so #+OPTION would be
> rendered the same as #+TITLE.  The gray would counter-balance the
> shouting of the capitals, making it more bearable.
>
> For lowercase multi-line environments keywords, red is just fine, and I
> did not see exceptions so far (which does not mean there are not any).

François,

Are you talking of a dark theme or light theme?  Did you take a look at Emacs
color themes, and their customization for Org?  See, for example, mine at
http://orgmode.org/worg/color-themes-screenshot.html#sec-1-4 [1].

In that page, you'll find:

- 6 dark themes
- 1 gray theme
- 1 light theme

Best regards,
  Seb

Footnotes:

[1] I should update my color-theme code and screenshot on Worg, as my color
theme has varied over the last months.

-- 
Sebastien Vauban

  parent reply	other threads:[~2012-01-11  7:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  3:19 Capitalisation and good taste ? François Pinard
2012-01-10  3:55 ` Bernt Hansen
2012-01-10  5:13   ` Nick Dokos
2012-01-10  5:35     ` François Pinard
2012-01-10  7:37       ` Nick Dokos
2012-01-10 14:59         ` François Pinard
2012-01-10 15:46           ` Nick Dokos
2012-01-10 19:32       ` Bastien
2012-01-10 19:38         ` Eric Schulte
2012-01-10 19:55           ` Bastien
2012-01-10 20:18             ` François Pinard
2012-01-10 20:57               ` Martyn Jago
2012-01-11  7:49               ` Sebastien Vauban [this message]
2012-01-14 22:15                 ` François Pinard
2012-01-14 23:01                   ` Sebastien Vauban
2012-01-11 15:40               ` Bastien
2012-01-14 22:25                 ` François Pinard
2012-01-11 15:38             ` Bastien
2012-01-11 20:47               ` Eric Schulte
2012-01-11 20:57                 ` Eric Schulte
2012-01-11 21:26                   ` [PATCH] " Thomas S. Dye
2012-01-11 22:42                     ` Eric Schulte
2012-01-12  7:42                   ` Bastien
2012-01-10  5:22   ` François Pinard
2012-01-10 17:45     ` Tommy Kelly
2012-01-10 21:19     ` Eric S Fraga
2012-01-10 23:41       ` Sankalp
2012-01-21  4:00   ` Leo Alekseyev
2012-01-21 12:16     ` Bernt Hansen
2012-01-21 20:08       ` Eric S Fraga
2012-01-21 23:03         ` Bernt Hansen
2012-01-23  8:49           ` Eric S Fraga
2012-01-24 14:42             ` Bastien
2012-01-10 21:13 ` Eric S Fraga

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=80hb02znjb.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).