From: "Henrik Hörmann" <leinfink@mailbox.org>
To: emacs-orgmode@gnu.org
Subject: Lowercase Properties Drawer?
Date: Wed, 15 Nov 2023 11:41:51 +0100 [thread overview]
Message-ID: <4304d287f869008ffa8331677e3d79d0f0ba7002.camel@mailbox.org> (raw)
In-Reply-To: 1eda1dda867c5f8ae02f6586d8f65b07ab6d79df.camel@mailbox.org
Hi!
It seems that inconsistencies with regard to lowercase/uppercase
conventions still abound. Is there a reason that `org-insert-property-
drawer' has a hardcoded `(insert ":PROPERTIES:\n:END:")'? I'd really
like to customize this.
(Sorry for the repeated mail, I sent the first one before I joined the
mailing list.)
next parent reply other threads:[~2023-11-15 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1eda1dda867c5f8ae02f6586d8f65b07ab6d79df.camel@mailbox.org>
2023-11-15 10:41 ` Henrik Hörmann [this message]
2023-11-15 10:53 ` Lowercase Properties Drawer? Ihor Radchenko
2023-11-15 10:55 ` Henrik Hörmann
2023-11-15 11:05 ` Ihor Radchenko
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=4304d287f869008ffa8331677e3d79d0f0ba7002.camel@mailbox.org \
--to=leinfink@mailbox.org \
--cc=emacs-orgmode@gnu.org \
/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).