From: Kaushal Modi <kaushal.modi@gmail.com>
To: Hanno Perrey <hanno@hoowl.se>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inconsistent handling of multi-line properties
Date: Mon, 28 Feb 2022 15:34:12 -0500 [thread overview]
Message-ID: <CAFyQvY1WgU=X0p6Xuh35DktAPryJoOJA_sDUQRKCB1UQtVoT9A@mail.gmail.com> (raw)
In-Reply-To: <185742ab-1719-540e-742c-5496ff61731d@hoowl.se>
On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey <hanno@hoowl.se> wrote:
>
> Hej,
>
> I have noticed that properties that stretch over multiple lines using
> the :value+: syntax are ignored by org-element-property and therefore
> also by e.g. org-export-get-node-property when exporting to ics via
> ox-icalendar.el (see example below). I was wondering now whether this is
> intentional and to be expected or a bug?
I use the :value+: syntax for the subtree properties regularly. For
exports, though, you need to prefix the properties with EXPORT_.
See the (org) Export Settings node in Org manual.
> When exporting sub-trees, special node properties can override the
above keywords. These properties have an ‘EXPORT_’ prefix. For
example, ‘DATE’ becomes, ‘EXPORT_DATE’ when used for a specific
sub-tree. Except for ‘SETUPFILE’, all other keywords listed above have
an ‘EXPORT_’ equivalent.
Here's one of the pathogenic test cases of ox-hugo:
=====
** Custom front matter in multiple lines
:PROPERTIES:
:EXPORT_FILE_NAME: custom-front-matter-multiple-lines
:EXPORT_DATE: 2017-07-24
:EXPORT_HUGO_CUSTOM_FRONT_MATTER: :foo bar
:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :baz zoo
:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :alpha 1
:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :beta "two words"
:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :gamma 10
:EXPORT_HUGO_CUSTOM_FRONT_MATTER+: :empty_string ""
:END:
=====
All the HUGO_CUSTOM_FRONT_MATTER properties get collected as expected.
Here's another example:
=====
#+author:
#+options: toc:nil
* Heading
:PROPERTIES:
:EXPORT_AUTHOR: abc def
:EXPORT_AUTHOR+: ghi jkl
:EXPORT_AUTHOR+: kmo pqr
:END:
=====
C-c C-e C-s t A exports to:
=====
_________________________
HEADING
abc def ghi jkl kmo pqr
_________________________
=====
next prev parent reply other threads:[~2022-02-28 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 15:01 Inconsistent handling of multi-line properties Hanno Perrey
2021-10-02 15:19 ` Ihor Radchenko
2022-02-28 20:09 ` Greg Sullivan
2022-03-20 5:47 ` Ihor Radchenko
2022-02-28 20:34 ` Kaushal Modi [this message]
2022-02-28 20:45 ` Kaushal Modi
2022-02-28 22:18 ` Greg Sullivan
2022-03-20 5:55 ` Ihor Radchenko
2024-01-22 11:17 ` Ihor Radchenko
2024-01-23 6:48 ` Jack Kamm
2024-01-25 13:35 ` Ihor Radchenko
2024-01-26 5:04 ` Jack Kamm
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='CAFyQvY1WgU=X0p6Xuh35DktAPryJoOJA_sDUQRKCB1UQtVoT9A@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hanno@hoowl.se \
/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).