From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: Capitalisation and good taste ?
Date: Wed, 11 Jan 2012 08:49:44 +0100
Message-ID: <80hb02znjb.fsf@somewhere.org>
References: <87k4509rc1.fsf@iro.umontreal.ca> <87aa5wcitv.fsf@norang.ca>
	<23144.1326172391@gamaville.dokosmarshall.org>
	<8762gk9l27.fsf@iro.umontreal.ca> <87wr8zwdz1.fsf@gnu.org>
	<87pqergxf6.fsf@gmx.com> <87ehv7wcx5.fsf@gnu.org>
	<87pqerfh0h.fsf@iro.umontreal.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode-mXXj517/zsQ@public.gmane.org>
List-Help: <mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org

Hi Bastien,

Fran=C3=A7ois 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=C3=A7ois,

Are you talking of a dark theme or light theme?  Did you take a look at Ema=
cs
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.

--=20
Sebastien Vauban