Great, thanks!
Hello,
Carlos Pita writes:
> Today I noticed the export templates inserted by org are still uppercase:
>
> #+LATEX_CLASS: article
> #+LATEX_CLASS_OPTIONS:
> #+LATEX_HEADER:
> #+LATEX_HEADER_EXTRA:
> #+DESCRIPTION:
> #+KEYWORDS:
> #+SUBTITLE:
> #+LATEX_COMPILER: pdflatex
>
> #+DATE: \today
>
>
Today I noticed the export templates inserted by org are still uppercase:
#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS:
#+LATEX_HEADER:
#+LATEX_HEADER_EXTRA:
#+DESCRIPTION:
#+KEYWORDS:
#+SUBTITLE:
#+LATEX_COMPILER: pdflatex
#+DATE: \today
Is this intentional, is the lowercase convention intended
On Tue, Feb 12, 2019 at 3:59 PM Carlos Pita
wrote:
> > What do you mean with the "uppercase legacy"? You mean all the current
> documents we already have?
>
> Specifically what motivated this post: collections of snippets that
> have been written with the historical convention in mind. It's easy
> What do you mean with the "uppercase legacy"? You mean all the current
> documents we already have?
Specifically what motivated this post: collections of snippets that
have been written with the historical convention in mind. It's easy to
convert them but it's not that easy to convert users
What do you mean with the "uppercase legacy"? You mean all the current
documents we already have?
In my case, those will remain with the upper case tags until I need to edit
them.
I guess it would be enough to patch the sites affected by
>
>
> At first I didn't like the lowercase tags for the blocks, but I got used to
> them after a couple of days.
I prefer the lowercase convention hands down. The problem I pointed
out is with the uppercase legacy.
> Someone suggested adding a defcustom option to org-tempo to let the user
> choose
Carlos,
I recently updated to 9.2 and was also confronted with the org-tempo
change.
At first I didn't like the lowercase tags for the blocks, but I got used to
them after a couple of days.
Someone suggested adding a defcustom option to org-tempo to let the user
choose between lower and upper
> Here are two previous threads about the subject:
>
> Last month:
> http://lists.gnu.org/archive/html/emacs-orgmode/2019-01/msg00349.html
> A year ago:
> http://lists.gnu.org/archive/html/emacs-orgmode/2018-01/msg00425.html
Interesting, thanks! Although the issue of mostly uppercase external
Carlos
Here are two previous threads about the subject:
- Last month:
http://lists.gnu.org/archive/html/emacs-orgmode/2019-01/msg00349.html
- A year ago:
http://lists.gnu.org/archive/html/emacs-orgmode/2018-01/msg00425.html
Regards
On Tue, Feb 12, 2019 at 9:51 AM Carlos Pita
> before, didn't they? Is this implying that now lowercase is preferred?
I dug this up from the repo:
org-element: Prefer lower case letters for blocks and keywords
https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0
So the answer is yes. Also the
Hi all,
I noticed that the default expansions for org-tempo in 9.2 are
lowercase. I think they followed the uppercase informal convention
before, didn't they? Is this implying that now lowercase is preferred?
Regards
--
Carlos
12 matches
Mail list logo