From: Kaushal Modi <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: Mon, 28 Feb 2022 15:45:22 -0500 [thread overview] Message-ID: <CAFyQvY3=_pE_oXmGFXx0jnL3KtF7ood4=TUAJ+nrJ_Vvemail@example.com> (raw) In-Reply-To: <CAFyQvY1WgU=X0p6Xuh35DktAPryJoOJA_sDUQRKCB1UQtVoT9A@mail.gmail.com> On Mon, Feb 28, 2022 at 3:34 PM Kaushal Modi <firstname.lastname@example.org> wrote: > > On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey <email@example.com> 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. Sorry, ignore my email noise. I had never tried ox-icalendar before. But I just tried it with your test snippet and it doesn't work as expected even with the EXPORT_ prefix. Also, I don't see any location info get exported to the .ics file (with or without the EXPORT_ prefix). So I don't know what I should expect to see in the .ics file.
next prev parent reply other threads:[~2022-02-28 20:47 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 [this message] 2022-02-28 22:18 ` Greg Sullivan 2022-03-20 5:55 ` 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='CAFyQvY3=_pE_oXmGFXx0jnL3KtF7ood4=TUAJ+nrJ_Vvfirstname.lastname@example.org' \ --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).