From: Timothy <tecosaur@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "Colin Baxter 😺" <m43cap@yandex.com>,
"Gyro Funch" <gyromagnetic@gmail.com>,
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: Tue, 11 Jan 2022 23:15:46 +0800 [thread overview]
Message-ID: <871r1emgjf.fsf@gmail.com> (raw)
In-Reply-To: <877db79cg7.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Hi Ihor,
> For some more context, other functions are not really consistent about uppercase/lowercase:
> - `org-insert-structure-template' lowercase
> - `org-insert-drawer' uppercase
> - `org-insert-property-drawer' uppercase
> - `org-babel-exp-code-template' defaults to uppercase
> - `org-clock-find-position' defaults to uppercase :END:
> - `org-feed-write-status' defaults to uppercase
> - `org-inlinetask-insert-task' defaults to uppercase
> - `org-mobile-write-agenda-for-mobile' defaults to uppercase
> - `org-babel-examplify-region' lowercase
Ok, I thought we were much closer to consistency than we seem to be. In that
case, I don’t see much point in /just/ changing #+results.
> So, unless there is overwhelming support for changing uppercase
> defaults into lowercase and a thorough patch, I am inclined towards
> preserving the existing behaviour.
I do think it would be nice if we went one way or the other (and from previous
discussion, lower case looks like the direction we’d go in), but it would have
to be across the board.
> Changing just RESULTS keyword provides no benefit to making things
> consistent.
Yep.
All the best,
Timothy
next prev parent reply other threads:[~2022-01-11 15:36 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
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 [this message]
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=871r1emgjf.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gyromagnetic@gmail.com \
--cc=m43cap@yandex.com \
--cc=yantar92@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).