From: Kaushal Modi <kaushal.modi@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: Gyro Funch <gyromagnetic@gmail.com>,
emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Prefer lowercase #+results [9.5.2 (release_9.5.2-3-geb9f34 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Date: Mon, 10 Jan 2022 09:34:28 -0500 [thread overview]
Message-ID: <CAFyQvY0JH3R6o9Li2Ou17k7yu+pDuJmqXMcYCJv4QAcdq=OtPg@mail.gmail.com> (raw)
In-Reply-To: <874k6bn38k.fsf@gmail.com>
On Mon, Jan 10, 2022 at 8:35 AM Timothy <tecosaur@gmail.com> wrote:
>
> FWIW, I think it would be good to be internally consistent. #+RESULTS is
> currently one of the few keywords inserted in upper case. Unless there’s a good
> reason to distinguish it from other keywords (perhaps an argument could be made
> that it should be treated differently because it is usually generated, not
> inserted by the user?), I’d be in favour of changing the default to be
> consistent.
+1 for consistency. The Org parser does not care if the keywords are
upper or lower case.
So inserting the #+results keyword in lower-case would be a good
change towards improving the consistency.
next prev parent reply other threads:[~2022-01-10 14:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 8:58 [BUG] Prefer lowercase #+results [9.5.2 (release_9.5.2-3-geb9f34 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)] Rudolf Adamkovič
2022-01-08 9:47 ` Colin Baxter 😺
2022-01-08 18:18 ` Rudolf Adamkovič
2022-01-08 21:29 ` Tim Cross
2022-01-09 17:21 ` Rudolf Adamkovič
2022-01-10 10:26 ` Gyro Funch
2022-01-10 13:09 ` Timothy
2022-01-10 14:34 ` Kaushal Modi [this message]
2022-01-10 15:31 ` Colin Baxter 😺
2022-01-11 3:30 ` Ihor Radchenko
2022-01-11 14:57 ` Colin Baxter 😺
2022-01-11 15:15 ` Timothy
2022-01-11 19:13 ` Rudolf Adamkovič
2022-01-11 19:53 ` William Denton
2022-01-11 20:30 ` Colin Baxter 😺
2022-01-12 14:17 ` Ihor Radchenko
2022-01-12 16:00 ` Christopher M. Miles
2022-01-12 16:35 ` Timothy
2022-01-13 1:43 ` Ihor Radchenko
2022-01-13 4:27 ` Timothy
2022-01-13 3:29 ` Christopher M. Miles
2022-01-13 4:33 ` Timothy
2022-01-13 5:25 ` Christopher M. Miles
2022-01-14 2:00 ` Ihor Radchenko
2022-01-14 4:23 ` Christopher M. Miles
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 \
--in-reply-to='CAFyQvY0JH3R6o9Li2Ou17k7yu+pDuJmqXMcYCJv4QAcdq=OtPg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gyromagnetic@gmail.com \
--cc=tecosaur@gmail.com \
/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 public 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).