From: Ihor Radchenko <email@example.com> To: Carlos Pita <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Shower thought: submit an IETF RFC to register Org as a MIME type Date: Sat, 23 Oct 2021 14:45:02 +0800 [thread overview] Message-ID: <87lf2k8ck1.fsf@localhost> (raw) In-Reply-To: <firstname.lastname@example.org> Carlos Pita <email@example.com> writes: >> Org is standardized on lower case. Uppercase is used in the manual as >> a poor man's bold, and supported for historical reasons. > > But C-c C-x p still inserts stuff like: > > :PROPERTIES: > :ARCHIVE: ... > :END: > > Maybe it should be updated or maybe I don't fully understand the > convention, perhaps it's just for blocks? The conversation was about keywords and similar constructs (i.e. ^#+keyword). You are looking at property drawer and properties inside. There is no preference here, though internally properties in property drawer are all converted to upper case. > But then c-a-p is very lenient since it lists lower and upper case block > variants even when I typed a lower case prefix, and upper case usually > will go first in the list, hence promoting a seemingly bad practice. Could you clarify what is "c-a-p"? Best, Ihor
next prev parent reply other threads:[~2021-10-23 6:44 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-22 1:21 Carlos Pita 2021-10-23 6:45 ` Ihor Radchenko [this message] 2021-10-23 8:34 ` Carlos Pita 2021-10-23 8:36 ` Timothy 2021-10-23 13:41 ` Keyword completion list: uppercase or lowercase? (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Ihor Radchenko 2021-10-23 13:51 ` Bruce D'Arcus 2021-10-23 14:21 ` Ihor Radchenko 2021-10-23 18:55 ` Keyword completion list: uppercase or lowercase? Carlos Pita -- strict thread matches above, loose matches on Subject: below -- 2020-09-24 20:25 Shower thought: submit an IETF RFC to register Org as a MIME type Andrea 2020-09-24 20:25 Andrea 2020-09-04 14:44 TEC 2020-09-04 16:14 ` Gustav Wikström 2020-09-05 5:30 ` stardiviner 2020-09-05 5:50 ` Bastien 2020-09-05 5:53 ` TEC 2020-09-17 7:09 ` TEC 2020-09-17 7:18 ` hj-orgmode-1 2020-09-23 7:31 ` Bastien 2020-10-01 3:40 ` TEC 2020-10-01 5:21 ` Bastien 2020-10-01 5:48 ` TEC 2020-10-01 6:46 ` Bastien 2020-10-01 15:39 ` Wes Hardaker 2020-10-01 15:45 ` TEC 2020-10-06 18:03 ` Wes Hardaker 2020-10-06 19:03 ` TEC 2020-10-06 20:39 ` Palak Mathur 2020-10-24 12:09 ` Bastien 2020-10-24 12:28 ` Palak Mathur 2020-10-24 12:50 ` Bastien 2020-10-24 13:09 ` Leo Vivier 2020-10-24 13:38 ` Bastien 2020-10-24 13:49 ` Leo Vivier 2020-10-24 15:12 ` Bastien 2020-10-24 15:00 ` Palak Mathur 2020-10-24 15:40 ` Bastien 2020-10-24 15:57 ` Palak Mathur 2020-10-14 9:52 ` Lennart C. Karssen 2020-10-14 14:22 ` Nicolas Goaziou 2021-03-23 3:00 ` Timothy
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=87lf2k8ck1.fsf@localhost \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Shower thought: submit an IETF RFC to register Org as a MIME type' \ /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
Code repositories for project(s) associated with this 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).