From: Kaushal Modi <kaushal.modi@gmail.com>
To: William Denton <wtd@pobox.com>, emacs-orgmode@gnu.org
Subject: Re: Upper or lower case in BEGIN_SRC and other keywords
Date: Thu, 16 Jun 2016 16:53:55 +0000 [thread overview]
Message-ID: <CAFyQvY1+bkw12L7FxZ0_pr9vBXqr0Q4Ek995SqDqPa+_GGUGBQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1606161207210.18358@shell.miskatonic.org>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
I believe that, in general, things are case-insensitive in org-mode. Please
do help clarify this if this is wrong.
The only place that I have come across as case-sensitive is the tag system.
If you tag a sub-tree with ':archive:', it will not be archived. The tag
has to be ':ARCHIVE:'.
On Thu, Jun 16, 2016 at 12:32 PM William Denton <wtd@pobox.com> wrote:
> When I use the <s shortcut for #+BEGIN_SRC, Org puts it in upper case. And
> #+RESULTS is in upper case too. I noticed other people have these
> keywords in
> lower case in examples or config files, so I looked in the manual, which
> says
> [1]
>
> "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."
>
> There's a footnote [2] that says:
>
> "Easy templates insert lowercase keywords and Babel dynamically inserts
> #+results."
>
> How come this doesn't happen for me? I don't see any variable that's
> making
> things default to upper case for me.
>
> This isn't a problem ... I'm just curious.
>
> Bill
>
> [1] http://orgmode.org/org.html#Conventions
> [2] http://orgmode.org/org.html#fn-3
>
> --
> William Denton :: Toronto, Canada :: https://www.miskatonic.org/
> Caveat lector.
>
> --
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
next prev parent reply other threads:[~2016-06-16 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 16:13 Upper or lower case in BEGIN_SRC and other keywords William Denton
2016-06-16 16:53 ` Kaushal Modi [this message]
2016-06-17 4:08 ` Bernhard Pröll
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY1+bkw12L7FxZ0_pr9vBXqr0Q4Ek995SqDqPa+_GGUGBQ@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.