From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Alsinet Subject: Re: Lowercase keywords in 9.2? Date: Tue, 12 Feb 2019 15:50:09 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d987100581b8923d" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:55381) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtf4k-0005SJ-Cf for emacs-orgmode@gnu.org; Tue, 12 Feb 2019 15:54:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtf0e-0001og-IY for emacs-orgmode@gnu.org; Tue, 12 Feb 2019 15:50:32 -0500 Received: from mail-ot1-f47.google.com ([209.85.210.47]:42834) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gtf0c-0001WC-E6 for emacs-orgmode@gnu.org; Tue, 12 Feb 2019 15:50:26 -0500 Received: by mail-ot1-f47.google.com with SMTP id i5so95487oto.9 for ; Tue, 12 Feb 2019 12:50:22 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Carlos Pita Cc: emacs-orgmode --000000000000d987100581b8923d Content-Type: text/plain; charset="UTF-8" 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 > > https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0 > and also the templates definition in org-tempo. Looking at that diff, the changes are not so simple as I initially thought, I was just thinking about patching org-tempo, but I guess they should cover all the uppercase tags. Now I don't feel so confident about doing it :-( Regards On Tue, Feb 12, 2019 at 11:10 AM Carlos Pita wrote: > > 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 > --000000000000d987100581b8923d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What do you mean with the "uppercase= legacy"? You mean all the current documents we already have?=C2=A0In my case, those will remain with the upper case tags until I need to ed= it them.

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

Looking at that diff, the changes a= re not so simple as I initially thought, I was just thinking about patching= org-tempo, but I guess they should cover all the uppercase tags.=C2=A0
Now I don't feel so confident about doing it :-(

<= /div>
Regards

On Tue, Feb 12, 2019 at 11:10 AM Carlos Pita = <carlosjosepita@gmail.com> wrote:
> At first I didn't like the = lowercase tags for the blocks, but I got used to them after a couple of day= s.

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 us= er choose between lower and upper case tags.
> It seems a simple enough feature for a first contribution. Maybe we co= uld 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.or= gmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0<= br> and also the templates definition in org-tempo.

Regards
--
Carlos
--000000000000d987100581b8923d--