From: Bernt Hansen <bernt@norang.ca>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Capitalisation and good taste ?
Date: Sat, 21 Jan 2012 07:16:36 -0500 [thread overview]
Message-ID: <87aa5h45ej.fsf@norang.ca> (raw)
In-Reply-To: <CADzxs1kfXcnQuOX2m1OQZCMGJAB=1h-LES6iypJnszTHCQSg+w@mail.gmail.com> (Leo Alekseyev's message of "Fri, 20 Jan 2012 22:00:24 -0600")
Leo Alekseyev <dnquark@gmail.com> writes:
>> A long time ago all capitals was the only way these keywords were
>> supported. Since then they have become case insensitive and I use all
>> lowercase for most of my keywords now (#+begin_src:, #+begin_example:
>> etc)
>>
>> With fontification these stand out enough now and the capitalization can
>> be removed.
>
> So I'm kind of late to this party, but like Bernt, I've been favoring
> lowercase #+ keywords; I believe it looks cleaner and easier on the
> eyes. However, if functions that autogenerate keywords (e.g.
> #+results from code blocks and easy templates) default to a particular
> case, forcing a different case as a user becomes unappealing
> (consistency trumps aesthetics).
>
> If we want to keep org truly keyword-case-agnostic, then there should
> be a user-customized variable that easy templates and org-babel result
> blocks would follow.
I added the following to my .emacs to keep lowercase.
(setq org-babel-results-keyword "results")
(setq org-structure-template-alist
(quote (("s" "#+begin_src ?\n\n#+end_src" "<src lang=\"?\">\n\n</src>")
("e" "#+begin_example\n?\n#+end_example" "<example>\n?\n</example>")
("q" "#+begin_quote\n?\n#+end_quote" "<quote>\n?\n</quote>")
("v" "#+begin_verse\n?\n#+end_verse" "<verse>\n?\n/verse>")
("c" "#+begin_center\n?\n#+end_center" "<center>\n?\n/center>")
("l" "#+begin_latex\n?\n#+end_latex" "<literal style=\"latex\">\n?\n</literal>")
("L" "#+latex: " "<literal style=\"latex\">?</literal>")
("h" "#+begin_html\n?\n#+end_html" "<literal style=\"html\">\n?\n</literal>")
("H" "#+html: " "<literal style=\"html\">?</literal>")
("a" "#+begin_ascii\n?\n#+end_ascii")
("A" "#+ascii: ")
("i" "#+index: ?" "#+index: ?")
("I" "#+include %file ?" "<include file=%file markup=\"?\">"))))
-Bernt
next prev parent reply other threads:[~2012-01-21 12:16 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
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 [this message]
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=87aa5h45ej.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=dnquark@gmail.com \
--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).