From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Cc: Bastien <bzg@gnu.org>, Bastien <bzg@altern.org>
Subject: Re: initiate source edits and region
Date: Sat, 04 May 2013 22:36:20 -0400 [thread overview]
Message-ID: <86txmib1az.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <5B474878-B7D8-4D29-83E9-B7DB8B3513D7@gmail.com> (Carsten Dominik's message of "Fri, 3 May 2013 15:36:54 +0200")
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?
>> The above command should also insert capitals, for Org being
>> consistent with itself :-)
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.
> I think this would be one more useful option to add.
An option could of course change how Org operates, but it would not
change the manual. The default or implicit value for that option should
then be consistent with the manual.
> - Carsten
François :-)
next prev parent reply other threads:[~2013-05-05 2:36 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 [this message]
2013-05-07 10:46 ` Bastien
2013-05-07 11:32 ` Carsten Dominik
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=86txmib1az.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--cc=bzg@altern.org \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).