all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: Martin Alsinet <martin@alsinet.com.ar>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Lowercase keywords in 9.2?
Date: Tue, 12 Feb 2019 13:09:41 -0300	[thread overview]
Message-ID: <CAELgYhf+vEL=_Z+9spo=yGbfrJ6pQdWZUpHE_m+ztY5cczsZPg@mail.gmail.com> (raw)
In-Reply-To: <CABUJmkDdzMDi03=Q1VkbA+DiRmb5wgbmKByTCzc_vGbUnW5rRA@mail.gmail.com>

> 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 between lower and upper case tags.
> It seems a simple enough feature for a first contribution. Maybe we could add it? I have never done it before, but I am willing to try.

I wouldn't mind (helping you) doing it as far as there is agreement
whether this is a desired option or not.

I guess it would be enough to patch the sites affected by
https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0
and also the templates definition in org-tempo.

Regards
--
Carlos

  reply	other threads:[~2019-02-12 16:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 13:19 Lowercase keywords in 9.2? Carlos Pita
2019-02-12 14:49 ` Carlos Pita
2019-02-12 15:23   ` Martin Alsinet
2019-02-12 15:30     ` Carlos Pita
2019-02-12 15:56       ` Martin Alsinet
2019-02-12 16:09         ` Carlos Pita [this message]
2019-02-12 20:50           ` Martin Alsinet
2019-02-12 20:57             ` Carlos Pita
2019-02-12 21:42               ` Kaushal Modi
2019-02-28 13:37                 ` Carlos Pita
2019-02-28 19:02                   ` Nicolas Goaziou
2019-02-28 19:20                     ` Carlos Pita

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAELgYhf+vEL=_Z+9spo=yGbfrJ6pQdWZUpHE_m+ztY5cczsZPg@mail.gmail.com' \
    --to=carlosjosepita@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=martin@alsinet.com.ar \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.