From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: initiate source edits and region
Date: Tue, 7 May 2013 13:32:26 +0200
Message-ID: <233873CD-2656-4E39-9A30-834A8C1FAF90@gmail.com>
References: <5183960F.4090402@easy-emacs.de> <86y5bw9v3s.fsf@somewhere.org>
	<86a9ocqjyc.fsf@iro.umontreal.ca>
	<5B474878-B7D8-4D29-83E9-B7DB8B3513D7@gmail.com>
	<86txmib1az.fsf@iro.umontreal.ca> <878v3r6oyk.fsf@bzg.ath.cx>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:34704)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <carsten.dominik@gmail.com>) id 1UZg8E-0007VO-MW
	for emacs-orgmode@gnu.org; Tue, 07 May 2013 07:32:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <carsten.dominik@gmail.com>) id 1UZg8C-0006Ms-ID
	for emacs-orgmode@gnu.org; Tue, 07 May 2013 07:32:30 -0400
In-Reply-To: <878v3r6oyk.fsf@bzg.ath.cx>
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@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <bzg@gnu.org>
Cc: =?iso-8859-1?Q?Fran=E7ois_Pinard?= <pinard@iro.umontreal.ca>, emacs-orgmode@gnu.org


On 7 mei 2013, at 12:46, Bastien <bzg@gnu.org> wrote:

> Hi Fran=E7ois and all,
>=20
> Fran=E7ois Pinard <pinard@iro.umontreal.ca> writes:
>=20
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>=20
>>>> In a previous mail list discussion on this (delicate, almost =
heated)
>>>> matter, Bastien finally ruled out that the preference in Org
>>>> documentation and behaviour should use capitals.
>>=20
>>> Could you please point me to that discussion?  Thanks.
>>=20
>> I tried for a few jiffies to find pointers.  I did find a few related
>> messages written around or before 2012-05, but not that one =
containing
>> Bastien's decision.  The simplest would be to write Bastien directly
>> (hoping he remembers).  Do you read us, Bastien?
>=20
> I do :) =20
>=20
> I remember I expressed a preference for capitals, but I don't
> remember if this was some policy I really wanted to enforce...
> I don't really care, actually.
>=20
>> Whatever the decision about capitals is retained or reversed, I would
>> surely like if the manual was using one convention consistently, and
>> that Org mode itself, while recognizing any capitalization, was
>> consistently generating the same which the manual uses, of course.
>=20
> This should be the case, the manual contains this paragraph:
>=20
>     Moreover, Org uses option keywords (like '#+TITLE' to set the =
title)
>  and environment keywords (like '#+BEGIN_HTML' to start a 'HTML'
>  environment).  They are written in uppercase in the manual to enhance
>  its readability, but you can use lowercase in your Org files(1)

I think the capitals make sense in the manual because it is viewed and =
printed in black and white, so here this is a good technique to make =
these keywords stick out.  I believe for working in a buffer where we =
have font-lock support, Org should cater to user preferences.

- Carsten


>=20
> HTH,
>=20
> --=20
> Bastien
>=20