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