From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org, "Rudolf Adamkovič" <salutis@me.com>
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: Fri, 14 Jan 2022 12:23:40 +0800 [thread overview]
Message-ID: <PAXPR08MB6640A1CDAD47BB745C1814EAA3549@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87bl0f5b6l.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Ihor Radchenko <yantar92@gmail.com> writes:
>> I suggest to keep current defaults. Because I have lot of Org files, if changed, I have to do lot of
>> work to adopt files and might get wrong. It's very important.
>
> Org mode does not distinguish the _meaning_ of all keywords regardless
> of their case. Including src blocks and results. If it is not the case,
> it should be a bug (and please report it then). So, you should have no
> need to change keyword case in your existing documents except for your
> visual satisfaction.
>
> What we are discussing here is the visual appearance of how the keywords
> are inserted by default. Nothing functional.
>
> Best,
> Ihor
That's the best, thanks for explanation.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-01-14 4:46 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
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 [this message]
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=PAXPR08MB6640A1CDAD47BB745C1814EAA3549@PAXPR08MB6640.eurprd08.prod.outlook.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=salutis@me.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).