From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gabriele Lana Subject: org-tempo violating org-mode conventions since 9.2 Date: Fri, 25 Jan 2019 15:05:00 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c33c8a058048d05a" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53420) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gn26e-0007HA-T2 for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 09:05:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gn26c-00032x-LC for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 09:05:16 -0500 Received: from mail-io1-xd2c.google.com ([2607:f8b0:4864:20::d2c]:32896) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gn26c-00031N-Fa for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 09:05:14 -0500 Received: by mail-io1-xd2c.google.com with SMTP id t24so7839916ioi.0 for ; Fri, 25 Jan 2019 06:05:13 -0800 (PST) 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: emacs-orgmode@gnu.org --000000000000c33c8a058048d05a Content-Type: text/plain; charset="UTF-8" Hi, following the conventions (https://orgmode.org/manual/Conventions.html) "Keywords and blocks are written in uppercase to enhance their readability" but since 9.2 all blocks inserted are lowercase, why? Is there a clean way to put them back in uppercase? I mean alse the ~BEGIN~ and ~END~ part of the blocks Thanks -- Gabriele Lana https://github.com/gabrielelana https://twitter.com/gabrielelana --000000000000c33c8a058048d05a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

= =C2=A0 following the conventions (https://orgmode.org/manual/Conventions.html) "Keywo= rds and blocks are written in uppercase to enhance their readability" = but since 9.2 all blocks inserted are lowercase, why?=C2=A0

<= /div>
Is there a clean way to put them back in uppercase? I mean alse t= he ~BEGIN~ and ~END~ part of the blocks

--000000000000c33c8a058048d05a-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amin Bandali Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Fri, 25 Jan 2019 11:04:28 -0500 Message-ID: <87pnskiv03.fsf@aminb.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:47700) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gn3y9-0002yA-2n for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 11:04:37 -0500 In-Reply-To: (Gabriele Lana's message of "Fri, 25 Jan 2019 15:05:00 +0100") 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: Gabriele Lana Cc: emacs-orgmode@gnu.org On 2019-01-25 3:05 PM, Gabriele Lana wrote: > Hi, > > following the conventions (https://orgmode.org/manual/Conventions.html) > "Keywords and blocks are written in uppercase to enhance their readabilit= y" > but since 9.2 all blocks inserted are lowercase, why? > > Is there a clean way to put them back in uppercase? I mean alse the ~BEGI= N~ > and ~END~ part of the blocks > Just to throw in my 2=C2=A2, I personally strongly prefer the less-obnoxious all-lowercase variant for all =E2=80=98#+=E2=80=99 keywords, though I do so= metimes use uppercase for things like #+TITLE or #+AUTHOR every now and again. I think it would be nice to provide a defcusom to allow choosing between upper vs. lowercase. As of now, you should be able to get all uppercase by customizing the `org-tempo-keywords-alist' list and by redefining `org-tempo-add-block' (for the =E2=80=9Cbegin=E2=80=9D and =E2=80=9Cend=E2= =80=9D parts) in org-tempo.el. > > Thanks > > --=20 > Gabriele Lana > https://github.com/gabrielelana > https://twitter.com/gabrielelana Best, amin From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Fri, 25 Jan 2019 18:01:18 +0100 Message-ID: <871s50zn6p.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:58934) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gn4rY-00027d-3y for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 12:01:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gn4rT-00077w-Ry for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 12:01:52 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:57019) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gn4rT-0006yy-II for emacs-orgmode@gnu.org; Fri, 25 Jan 2019 12:01:47 -0500 In-Reply-To: (Gabriele Lana's message of "Fri, 25 Jan 2019 15:05:00 +0100") 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: Gabriele Lana Cc: emacs-orgmode@gnu.org Hello, Gabriele Lana writes: > following the conventions (https://orgmode.org/manual/Conventions.html) > "Keywords and blocks are written in uppercase to enhance their readability" > but since 9.2 all blocks inserted are lowercase, why? To make it clear, this convention is for the /manual/ only, not for Org syntax. Blocks are case insensitive. Regards, -- Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Welle Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Sat, 26 Jan 2019 09:11:15 +0100 Message-ID: <87o983rg7w.fsf@luisa.c0t0d0s0.de> References: <87pnskiv03.fsf@aminb.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59132) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnJ48-0001jk-Dk for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 03:11:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnJ45-0007Fw-2D for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 03:11:48 -0500 Received: from mout.gmx.net ([212.227.15.19]:55535) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gnJ44-0005OR-Kn for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 03:11:44 -0500 Received: from stella.c0t0d0s0.de ([89.204.154.102]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MNZ9u-1gq2t43WiA-007Bup for ; Sat, 26 Jan 2019 09:11:17 +0100 Received: from Stella (stella.c0t0d0s0.de [192.168.42.1]) by stella.c0t0d0s0.de (Postfix) with ESMTP id C4FDA181138 for ; Sat, 26 Jan 2019 09:11:15 +0100 (CET) In-Reply-To: <87pnskiv03.fsf@aminb.org> (Amin Bandali's message of "Fri, 25 Jan 2019 11:04:28 -0500") 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: emacs-orgmode@gnu.org Hello, Amin Bandali writes: [...] > I think it would be nice to provide a defcusom to allow choosing between > upper vs. lowercase. that would make the exchange of Org files with colleagues and other Org aficionados complicated, wouldn't it? As Nicolas said, blocks are case-insensitive, meaning one could write them down according to one's liking ;). Regards hmw -- FrOSCon? Free and Open Source Software Conference 10th + 11th August 2019, Sankt Augustin, Bonn Area/Germany https://www.froscon.de/en/ From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Cross Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Sat, 26 Jan 2019 19:58:53 +1100 Message-ID: <87pnsj3icy.fsf@gmail.com> References: <87pnskiv03.fsf@aminb.org> <87o983rg7w.fsf@luisa.c0t0d0s0.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:43012) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnJnu-0001OZ-NW for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 03:59:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnJns-0004V1-TU for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 03:59:05 -0500 Received: from mail-pl1-x62a.google.com ([2607:f8b0:4864:20::62a]:45167) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gnJns-0004DI-NE for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 03:59:04 -0500 Received: by mail-pl1-x62a.google.com with SMTP id a14so5610942plm.12 for ; Sat, 26 Jan 2019 00:59:02 -0800 (PST) Received: from tim-desktop (2001-44b8-31f2-bb00-2037-3410-a886-f561.static.ipv6.internode.on.net. [2001:44b8:31f2:bb00:2037:3410:a886:f561]) by smtp.gmail.com with ESMTPSA id m9sm65751084pgd.32.2019.01.26.00.58.58 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 26 Jan 2019 00:58:59 -0800 (PST) In-reply-to: <87o983rg7w.fsf@luisa.c0t0d0s0.de> 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: emacs-orgmode@gnu.org I totally agree that block delimiters should be case insensitive. However, I think the ability for a user to set their preference for either upper case or lower case is reasonable. It does not need to affect the syntactic interpretation, just whether the template system does it in upper case or lower case. I have no idea how much more complex this would make the tempo definitions though. Tim Michael Welle writes: > Hello, > > Amin Bandali writes: > [...] >> I think it would be nice to provide a defcusom to allow choosing between >> upper vs. lowercase. > that would make the exchange of Org files with colleagues and other Org > aficionados complicated, wouldn't it? As Nicolas said, blocks are > case-insensitive, meaning one could write them down according to one's > liking ;). > > Regards > hmw -- Tim Cross From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Welle Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Sat, 26 Jan 2019 10:47:30 +0100 Message-ID: <87va2bbvil.fsf@luisa.c0t0d0s0.de> References: <87pnskiv03.fsf@aminb.org> <87o983rg7w.fsf@luisa.c0t0d0s0.de> <87pnsj3icy.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51133) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnKYz-000883-Hb for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 04:47:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnKYv-0005sy-5w for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 04:47:42 -0500 Received: from mout.gmx.net ([212.227.15.15]:52719) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gnKYu-0005L7-Ou for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 04:47:41 -0500 Received: from stella.c0t0d0s0.de ([89.204.154.102]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MFtf4-1gzxbB3Hvy-00EyuD for ; Sat, 26 Jan 2019 10:47:31 +0100 Received: from Stella (stella.c0t0d0s0.de [192.168.42.1]) by stella.c0t0d0s0.de (Postfix) with ESMTP id C1DDD181138 for ; Sat, 26 Jan 2019 10:47:30 +0100 (CET) In-Reply-To: <87pnsj3icy.fsf@gmail.com> (Tim Cross's message of "Sat, 26 Jan 2019 19:58:53 +1100") 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: emacs-orgmode@gnu.org Hello, Tim Cross writes: > I totally agree that block delimiters should be case > insensitive. However, I think the ability for a user to set their > preference for either upper case or lower case is reasonable. It does > not need to affect the syntactic interpretation, just whether the > template system does it in upper case or lower case. I have no idea how > much more complex this would make the tempo definitions though. ah, I understand. I had the generating part as well as the parsing part in mind when I wrote my last posting. But you are right, making customisable how the blocks are generated wouldn't hurt anyone, I think. Maybe it is enough to change org-create-dblock, maybe there are more places to look at. Regards hmw From mboxrd@z Thu Jan 1 00:00:00 1970 From: stardiviner Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Sun, 27 Jan 2019 10:56:19 +0800 Message-ID: <87tvhuhkq4.fsf@gmail.com> References: <87pnskiv03.fsf@aminb.org> <87o983rg7w.fsf@luisa.c0t0d0s0.de> <87pnsj3icy.fsf@gmail.com> Reply-To: numbchild@gmail.com Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:57173) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnaYw-0004eB-Ft for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 21:52:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnaYv-0002Sn-6c for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 21:52:46 -0500 Received: from [122.236.17.38] (port=51402 helo=dark.localdomain) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnaYu-0002SK-QC for emacs-orgmode@gnu.org; Sat, 26 Jan 2019 21:52:45 -0500 In-reply-to: <87pnsj3icy.fsf@gmail.com> 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: emacs-orgmode@gnu.org Tim Cross writes: > I totally agree that block delimiters should be case > insensitive. However, I think the ability for a user to set their > preference for either upper case or lower case is reasonable. It does > not need to affect the syntactic interpretation, just whether the > template system does it in upper case or lower case. I have no idea how > much more complex this would make the tempo definitions though. > > Tim > > Michael Welle writes: > >> Hello, >> >> Amin Bandali writes: >> [...] >>> I think it would be nice to provide a defcusom to allow choosing between >>> upper vs. lowercase. >> that would make the exchange of Org files with colleagues and other Org >> aficionados complicated, wouldn't it? As Nicolas said, blocks are >> case-insensitive, meaning one could write them down according to one's >> liking ;). >> >> Regards >> hmw I agree. I upvote an option for this option. I remember there is an option before, but someday it's gone. Now still has a similar option `org-babel-uppercase-example-markers'. They can be merged if someone want to add a patch. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gabriele Lana Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Sun, 27 Jan 2019 16:50:32 +0100 Message-ID: References: <871s50zn6p.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000ddf8b505807285ac" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60254) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnmhr-0001yj-Fk for emacs-orgmode@gnu.org; Sun, 27 Jan 2019 10:50:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnmhq-0007qo-DI for emacs-orgmode@gnu.org; Sun, 27 Jan 2019 10:50:47 -0500 Received: from mail-it1-x133.google.com ([2607:f8b0:4864:20::133]:33236) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gnmhq-0007oH-5u for emacs-orgmode@gnu.org; Sun, 27 Jan 2019 10:50:46 -0500 Received: by mail-it1-x133.google.com with SMTP id m8so8993273itk.0 for ; Sun, 27 Jan 2019 07:50:45 -0800 (PST) In-Reply-To: <871s50zn6p.fsf@nicolasgoaziou.fr> 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: emacs-orgmode@gnu.org --000000000000ddf8b505807285ac Content-Type: text/plain; charset="UTF-8" On Fri, 25 Jan 2019 at 18:01, Nicolas Goaziou wrote: > > following the conventions (https://orgmode.org/manual/Conventions.html > ) > > "Keywords and blocks are written in uppercase to enhance their > readability" > > but since 9.2 all blocks inserted are lowercase, why? > > To make it clear, this convention is for the /manual/ only, not for Org > syntax. Blocks are case insensitive. > Thanks for the clarification, still, it seems odd that the manual uses a convention that Org (since 9.2) kind of force you to break Ex. if I want to wrap a result from a source block evaluation the ~begin_~ and ~end_~ tags will be lowercase unless I start to advice functions I'm quite puzzled because it seems an arbitrary choice forced to the user with no clear reasons -- Gabriele Lana https://github.com/gabrielelana https://twitter.com/gabrielelana --000000000000ddf8b505807285ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, 25 Jan 2019 at 18:01, Nicolas Goa= ziou <mail@nicolasgoaziou.fr> wrote:
>=C2=A0 =C2=A0following the conventions (https://orgmo= de.org/manual/Conventions.html)
> "Keywords and blocks are written in uppercase to enhance their re= adability"
> but since 9.2 all blocks inserted are lowercase, why?

To make it clear, this convention is for the /manual/ only, not for Org
syntax. Blocks are case insensitive.

Th= anks for the clarification, still, it seems odd that the manual uses a conv= ention that Org (since 9.2) kind of force you to break

=
Ex. if I want to wrap a result from a source block evaluation the ~beg= in_~ and ~end_~ tags will be lowercase unless I start to advice functions

I'm quite puzzled because it seems an arbitrary= choice forced to the user with no clear reasons
=C2=A0
=
--
Gabriele Lana
https://github.= com/gabrielelana
https://twitter.com/gabrielelana
--000000000000ddf8b505807285ac-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gabriele Lana Subject: Re: org-tempo violating org-mode conventions since 9.2 Date: Sun, 27 Jan 2019 17:24:23 +0100 Message-ID: References: <87pnskiv03.fsf@aminb.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000e3071f058072fef0" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:36769) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gnnEf-00007L-3p for emacs-orgmode@gnu.org; Sun, 27 Jan 2019 11:24:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gnnEc-0007iy-Pj for emacs-orgmode@gnu.org; Sun, 27 Jan 2019 11:24:41 -0500 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]:41935) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gnnEc-0007iH-1G for emacs-orgmode@gnu.org; Sun, 27 Jan 2019 11:24:38 -0500 Received: by mail-io1-xd33.google.com with SMTP id s22so11515311ioc.8 for ; Sun, 27 Jan 2019 08:24:35 -0800 (PST) In-Reply-To: <87pnskiv03.fsf@aminb.org> 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: emacs-orgmode@gnu.org --000000000000e3071f058072fef0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 25 Jan 2019 at 17:04, Amin Bandali wrote: > Just to throw in my 2=C2=A2, I personally strongly prefer the less-obnoxi= ous > all-lowercase variant for all =E2=80=98#+=E2=80=99 keywords, though I do = sometimes use > uppercase for things like #+TITLE or #+AUTHOR every now and again. > > I think it would be nice to provide a defcusom to allow choosing between > upper vs. lowercase. As of now, you should be able to get all uppercase > by customizing the `org-tempo-keywords-alist' list and by redefining > `org-tempo-add-block' (for the =E2=80=9Cbegin=E2=80=9D and =E2=80=9Cend= =E2=80=9D parts) in org-tempo.el. > +1 for the ~defcustom~ :-) --=20 Gabriele Lana https://github.com/gabrielelana https://twitter.com/gabrielelana --000000000000e3071f058072fef0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, 25 Jan 2019 at 17:04, Amin Bandal= i <bandali@gnu.org> wrote:
=
Just to throw in my 2=C2=A2, I personally strongly prefer the less-= obnoxious
all-lowercase variant for all =E2=80=98#+=E2=80=99 keywords, though I do so= metimes use
uppercase for things like #+TITLE or #+AUTHOR every now and again.

I think it would be nice to provide a defcusom to allow choosing between upper vs. lowercase.=C2=A0 As of now, you should be able to get all upperca= se
by customizing the `org-tempo-keywords-alist' list and by redefining `org-tempo-add-block' (for the =E2=80=9Cbegin=E2=80=9D and =E2=80=9Cend= =E2=80=9D parts) in org-tempo.el.

+1 fo= r the ~defcustom~ :-)
=C2=A0
--
--000000000000e3071f058072fef0--