Re: org-tempo violating org-mode conventions since 9.2

[stardiviner <numbchild@gmail.com>]

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