From: Ihor Radchenko <firstname.lastname@example.org> To: Hanno Perrey <email@example.com> Cc: emacs-orgmode <firstname.lastname@example.org> Subject: Re: Inconsistent handling of multi-line properties Date: Sun, 20 Mar 2022 13:55:07 +0800 [thread overview] Message-ID: <87o821dv7o.fsf@localhost> (raw) In-Reply-To: <email@example.com> Hanno Perrey <firstname.lastname@example.org> writes: > 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? > > * heading with multi-line property > :PROPERTIES: > :LOCATION: Someplace > :LOCATION+: Some Street 5 > :LOCATION+: 12345 Small Town > :END: Confirmed. I am not sure if this should be fixed on org-export-get-node-property level. Icalendar may want to concatenate the multi-line property specially. The usual Org approach is merging such properties into a single line. I can see multiple solutions: 1. Change Org's behaviour globally and make org-element-property return a list for multi-line properties. This will likely break things, but I would be in favour, unless Nicolas disagrees. 2. Change org-export-get-node-property to behave like org-entry-get and concatenate multi-line properties into a single line 3. Change ox-icalendar to consider :LOCATION+ properties and merge them during export. Best, Ihor
prev parent reply other threads:[~2022-03-20 5:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-02 15:01 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 2022-02-28 20:45 ` Kaushal Modi 2022-02-28 22:18 ` Greg Sullivan 2022-03-20 5:55 ` Ihor Radchenko [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=87o821dv7o.fsf@localhost \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Inconsistent handling of multi-line properties' \ /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).