From: Eric Schulte <eric.schulte@gmx.com>
To: Bastien <bzg@altern.org>
Cc: "Bernt Hansen" <bernt@norang.ca>,
"François Pinard" <pinard@iro.umontreal.ca>,
nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Capitalisation and good taste ?
Date: Tue, 10 Jan 2012 12:38:53 -0700 [thread overview]
Message-ID: <87pqergxf6.fsf@gmx.com> (raw)
In-Reply-To: <87wr8zwdz1.fsf@gnu.org> (Bastien's message of "Tue, 10 Jan 2012 20:32:18 +0100")
Bastien <bzg@altern.org> writes:
> Hi François,
>
> pinard@iro.umontreal.ca (François Pinard) writes:
>
>> P.P.S. How about amending the manual for consistent capitalization?
>
> I've pushed a fix for this.
>
> The manual used mostly uppercase so I fixed the few lowercase
> instances of option/environment keywords.
>
> I made an exception for #+results, which is dynamically used
> with lowercase.
>
> For the historical note: Carsten used uppercase most of the
> time, and Eric introduced lowercase. To me, uppercase looks
> better in the manual, and also means "this is a predefined
> keyword (see the other rules for TODO, tags and properties.)
>
> Thanks for raising this,
Ah! I don't mean to introduce inconsistencies. I would be happy to
change the dynamic #+results: generation so that it instead inserts
#+RESULTS: into the buffer. I believe the gain in consistency
out-weights any aesthetic concerns.
That said I'm happy that Org-mode is forgiving enough to allow me to
lowercase most of my keywords locally.
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-01-10 19:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 3:19 Capitalisation and good taste ? François Pinard
2012-01-10 3:55 ` Bernt Hansen
2012-01-10 5:13 ` Nick Dokos
2012-01-10 5:35 ` François Pinard
2012-01-10 7:37 ` Nick Dokos
2012-01-10 14:59 ` François Pinard
2012-01-10 15:46 ` Nick Dokos
2012-01-10 19:32 ` Bastien
2012-01-10 19:38 ` Eric Schulte [this message]
2012-01-10 19:55 ` Bastien
2012-01-10 20:18 ` François Pinard
2012-01-10 20:57 ` Martyn Jago
2012-01-11 7:49 ` Sebastien Vauban
2012-01-14 22:15 ` François Pinard
2012-01-14 23:01 ` Sebastien Vauban
2012-01-11 15:40 ` Bastien
2012-01-14 22:25 ` François Pinard
2012-01-11 15:38 ` Bastien
2012-01-11 20:47 ` Eric Schulte
2012-01-11 20:57 ` Eric Schulte
2012-01-11 21:26 ` [PATCH] " Thomas S. Dye
2012-01-11 22:42 ` Eric Schulte
2012-01-12 7:42 ` Bastien
2012-01-10 5:22 ` François Pinard
2012-01-10 17:45 ` Tommy Kelly
2012-01-10 21:19 ` Eric S Fraga
2012-01-10 23:41 ` Sankalp
2012-01-21 4:00 ` Leo Alekseyev
2012-01-21 12:16 ` Bernt Hansen
2012-01-21 20:08 ` Eric S Fraga
2012-01-21 23:03 ` Bernt Hansen
2012-01-23 8:49 ` Eric S Fraga
2012-01-24 14:42 ` Bastien
2012-01-10 21:13 ` Eric S Fraga
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=87pqergxf6.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=bernt@norang.ca \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--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).