From mboxrd@z Thu Jan  1 00:00:00 1970
From: stardiviner <numbchild@gmail.com>
Subject: Re: org-tempo violating org-mode conventions since 9.2
Date: Sun, 27 Jan 2019 10:56:19 +0800
Message-ID: <87tvhuhkq4.fsf@gmail.com>
References: <CA+bK9UF9O73Anz8d33+8BGkWjM_ahtNx0nNMa7pB4uJMbCUzCQ@mail.gmail.com>
	<87pnskiv03.fsf@aminb.org> <87o983rg7w.fsf@luisa.c0t0d0s0.de>
	<87pnsj3icy.fsf@gmail.com>
Reply-To: numbchild@gmail.com
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:57173)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <numbchild@gmail.com>) id 1gnaYw-0004eB-Ft
	for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 21:52:47 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <numbchild@gmail.com>) id 1gnaYv-0002Sn-6c
	for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 21:52:46 -0500
Received: from [122.236.17.38] (port=51402 helo=dark.localdomain)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <numbchild@gmail.com>) id 1gnaYu-0002SK-QC
	for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 21:52:45 -0500
In-reply-to: <87pnsj3icy.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-orgmode@gnu.org


Tim Cross <theophilusx@gmail.com> writes:

> I totally agree that block delimiters should be case
> insensitive. However, I think the ability for a user to set their
> preference for either upper case or lower case is reasonable. It does
> not need to affect the syntactic interpretation, just whether the
> template system does it in upper case or lower case. I have no idea how
> much more complex this would make the tempo definitions though.
>
> Tim
>
> Michael Welle <mwe012008@gmx.net> writes:
>
>> Hello,
>>
>> Amin Bandali <bandali@gnu.org> writes:
>> [...]
>>> I think it would be nice to provide a defcusom to allow choosing between
>>> upper vs. lowercase.
>> that would make the exchange of Org files with colleagues and other Org
>> aficionados complicated, wouldn't it? As Nicolas said, blocks are
>> case-insensitive, meaning one could write them down according to one's
>> liking ;). 
>>
>> Regards
>> hmw

I agree. I upvote an option for this option. I remember there is an
option before, but someday it's gone. Now still has a similar option
`org-babel-uppercase-example-markers'. They can be merged if someone
want to add a patch.

-- 
[ stardiviner ]
       I try to make every word tell the meaning what I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3