From: Gabriele Lana <gabriele.lana@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-tempo violating org-mode conventions since 9.2
Date: Sun, 27 Jan 2019 16:50:32 +0100 [thread overview]
Message-ID: <CA+bK9UE6qQ6CH_Lo+Q+wSz60ZcdGMNZ0vAmeitZ+ZduQBWh=2g@mail.gmail.com> (raw)
In-Reply-To: <871s50zn6p.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Fri, 25 Jan 2019 at 18:01, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> > following the conventions (https://orgmode.org/manual/Conventions.html
> )
> > "Keywords and blocks are written in uppercase to enhance their
> readability"
> > but since 9.2 all blocks inserted are lowercase, why?
>
> To make it clear, this convention is for the /manual/ only, not for Org
> syntax. Blocks are case insensitive.
>
Thanks for the clarification, still, it seems odd that the manual uses a
convention that Org (since 9.2) kind of force you to break
Ex. if I want to wrap a result from a source block evaluation the ~begin_~
and ~end_~ tags will be lowercase unless I start to advice functions
I'm quite puzzled because it seems an arbitrary choice forced to the user
with no clear reasons
--
Gabriele Lana
https://github.com/gabrielelana
https://twitter.com/gabrielelana
[-- Attachment #2: Type: text/html, Size: 1544 bytes --]
prev parent reply other threads:[~2019-01-27 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 14:05 org-tempo violating org-mode conventions since 9.2 Gabriele Lana
2019-01-25 16:04 ` Amin Bandali
2019-01-26 8:11 ` Michael Welle
2019-01-26 8:58 ` Tim Cross
2019-01-26 9:47 ` Michael Welle
2019-01-27 2:56 ` stardiviner
2019-01-27 16:24 ` Gabriele Lana
2019-01-25 17:01 ` Nicolas Goaziou
2019-01-27 15:50 ` Gabriele Lana [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='CA+bK9UE6qQ6CH_Lo+Q+wSz60ZcdGMNZ0vAmeitZ+ZduQBWh=2g@mail.gmail.com' \
--to=gabriele.lana@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).