From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "François Pinard" <pinard@iro.umontreal.ca>, emacs-orgmode@gnu.org
Subject: Re: initiate source edits and region
Date: Tue, 7 May 2013 13:32:26 +0200 [thread overview]
Message-ID: <233873CD-2656-4E39-9A30-834A8C1FAF90@gmail.com> (raw)
In-Reply-To: <878v3r6oyk.fsf@bzg.ath.cx>
On 7 mei 2013, at 12:46, Bastien <bzg@gnu.org> wrote:
> Hi François and all,
>
> François Pinard <pinard@iro.umontreal.ca> writes:
>
>> Carsten Dominik <carsten.dominik@gmail.com> 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
>
prev parent reply other threads:[~2013-05-07 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 10:48 initiate source edits and region Andreas Röhler
2013-05-03 11:11 ` Sebastien Vauban
2013-05-03 11:22 ` Andreas Röhler
2013-05-03 13:19 ` François Pinard
2013-05-03 13:35 ` Sebastien Vauban
2013-05-03 13:36 ` Carsten Dominik
2013-05-05 2:36 ` François Pinard
2013-05-07 10:46 ` Bastien
2013-05-07 11:32 ` Carsten Dominik [this message]
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=233873CD-2656-4E39-9A30-834A8C1FAF90@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).