emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsuucat <tsuucat@icloud.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why not org-tempo insert upcased strings?
Date: Sat, 25 Apr 2020 14:09:39 +0900	[thread overview]
Message-ID: <FF5A8928-7BAC-4BAD-9E68-181AACF30D97@icloud.com> (raw)
In-Reply-To: <CAFyQvY3rHHDBkdS7hBGM-Fj=MZ8QCkgEfLDGXnfywPs922DVCQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

> Yes, the convention is now to have downcased keywords. 
Thanks. Is the convention documented?

https://orgmode.org/manual/Structure-Templates.html#Structure-Templates <https://orgmode.org/manual/Structure-Templates.html#Structure-Templates>
It doesn’t seems that The Org Manual uses such a convention.


[-- Attachment #2: Type: text/html, Size: 1119 bytes --]

  reply	other threads:[~2020-04-25  5:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 15:05 tsuucat
2020-04-24 12:36 ` Kaushal Modi
2020-04-25  5:09   ` tsuucat [this message]
2020-04-25  5:43     ` Kyle Meyer
2020-04-27  8:35       ` tsuucat
2020-04-27 12:16         ` Kaushal Modi
2020-04-27 18:49           ` Kyle Meyer

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:

  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=FF5A8928-7BAC-4BAD-9E68-181AACF30D97@icloud.com \
    --to=tsuucat@icloud.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --subject='Re: Why not org-tempo insert upcased strings?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).