Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-27 Thread Gabriele Lana
On Fri, 25 Jan 2019 at 17:04, Amin Bandali wrote: > Just to throw in my 2¢, I personally strongly prefer the less-obnoxious > all-lowercase variant for all ‘#+’ keywords, though I do sometimes use > uppercase for things like #+TITLE or #+AUTHOR every now and again. > > I think it would be nice

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-27 Thread Gabriele Lana
On Fri, 25 Jan 2019 at 18:01, Nicolas Goaziou 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,

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-26 Thread stardiviner
Tim Cross 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

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-26 Thread Michael Welle
Hello, Tim Cross 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 >

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-26 Thread Tim Cross
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

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-26 Thread Michael Welle
Hello, Amin Bandali 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

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-25 Thread Nicolas Goaziou
Hello, Gabriele Lana writes: > 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/

Re: [O] org-tempo violating org-mode conventions since 9.2

2019-01-25 Thread Amin Bandali
On 2019-01-25 3:05 PM, Gabriele Lana wrote: > Hi, > > 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? > > Is there a clean way to put

[O] org-tempo violating org-mode conventions since 9.2

2019-01-25 Thread Gabriele Lana
Hi, 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? Is there a clean way to put them back in uppercase? I mean alse the ~BEGIN~ and ~END~