From: Kyle Meyer <firstname.lastname@example.org> To: Kaushal Modi <email@example.com>, tsuucat <firstname.lastname@example.org> Cc: emacs-org list <email@example.com> Subject: Re: Why not org-tempo insert upcased strings? Date: Mon, 27 Apr 2020 18:49:11 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAFyQvY3+3JsW0SeyoVgXiXuaJG_rSQntio3A-4X1xEC=0LNoNw@mail.gmail.com> Kaushal Modi <email@example.com> writes: > On Mon, Apr 27, 2020, 4:35 AM tsuucat <firstname.lastname@example.org> wrote: > >> Why the convention is changed in org-tempo? > > I'm a bit hazy about this, but I believe that org-tempo got introduced > after this commit: > https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0 org-tempo was added in 94f1a5843 (org-tempo.el: New file for expansion of templates, 2017-12-05) and already existed at the time of that commit, 13424336a (org-element: Prefer lower case letters for blocks and keywords, 2018-01-24). $ git ls-tree -r 13424336a6f30c50952d291e7a82906c1210daf0 | grep tempo 100644 blob 38d21de5e15b8fed0ac0a2b7737064e2a7842350 lisp/org-tempo.el 100644 blob 20062feebe108a0cb9a32f2bf9bb6fdd03924833 testing/lisp/test-org-tempo.el > This was a few years ago. There was even a discussion thread on this list > that showed preference to make that change. > > https://lists.gnu.org/archive/html/emacs-orgmode/2017-10/msg00449.html I'm just a passive observer, but I agree that that message (email@example.com) is probably the key one to point to. It belongs to the thread that led to c04e357f3 (Replace easy templates with org-insert-structure-template, 2017-11-05). At that point, the upper-case-inserting easy templates were replaced by the lower-case-inserting org-insert-structure-template command. Shortly after, Rasmus introduced org-tempo (https://firstname.lastname@example.org/), which restored the ability for easy-template-like "<s" expansion, but using org-structure-template-alist and keeping with the decision to use lower case.
prev parent reply other threads:[~2020-04-27 18:49 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 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 [this message]
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Why not org-tempo insert upcased strings?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * 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: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).