[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] initiate source edits and region
From: |
Carsten Dominik |
Subject: |
Re: [O] initiate source edits and region |
Date: |
Tue, 7 May 2013 13:32:26 +0200 |
On 7 mei 2013, at 12:46, Bastien <address@hidden> wrote:
> Hi François and all,
>
> François Pinard <address@hidden> writes:
>
>> Carsten Dominik <address@hidden> writes:
>>
>>>> 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.
>>
>>> Could you please point me to that discussion? Thanks.
>>
>> 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?
>
> I do :)
>
> 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.
>
>> 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.
>
> This should be the case, the manual contains this paragraph:
>
> 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
>
> HTH,
>
> --
> Bastien
>