From mboxrd@z Thu Jan 1 00:00:00 1970 From: pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) Subject: Re: Capitalisation and good taste ? Date: Tue, 10 Jan 2012 15:18:38 -0500 Message-ID: <87pqerfh0h.fsf@iro.umontreal.ca> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:45752) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rki9b-0002Gf-HM for emacs-orgmode@gnu.org; Tue, 10 Jan 2012 15:18:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rki9X-0000z3-TS for emacs-orgmode@gnu.org; Tue, 10 Jan 2012 15:18:43 -0500 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:51980 helo=mercure.epsilon-ti.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rki9X-0000yv-ON for emacs-orgmode@gnu.org; Tue, 10 Jan 2012 15:18:39 -0500 In-Reply-To: <87ehv7wcx5.fsf@gnu.org> (Bastien's message of "Tue, 10 Jan 2012 20:55:02 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Bernt Hansen , nicholas.dokos@hp.com, emacs-orgmode@gnu.org, Eric Schulte Bastien writes: > Eric Schulte 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! :-). 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