From: Jack Kamm <jackkamm@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>,
Ihor Radchenko <yantar92@gmail.com>
Cc: Hanno Perrey <hanno@hoowl.se>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inconsistent handling of multi-line properties
Date: Mon, 22 Jan 2024 22:48:51 -0800 [thread overview]
Message-ID: <87il3ka6jw.fsf@gmail.com> (raw)
In-Reply-To: <87ede9vcqz.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>>> 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?
>
>> 3. Change ox-icalendar to consider :LOCATION+ properties and merge them
>> during export.
>
> I went with this approach.
> See the attached tentative patch.
Thanks Ihor -- this is a nice improvement for ox-icalendar.
My only suggestion would be to add this information and your small
location example to the manual.
> CCing Jack - you expressed interest in ox-icalendar in the past.
>
> P.S. We need a maintainer for ox-icalendar ;)
Sure, I'm happy to help with this :)
Please forward/CC any issues you'd like me to look at. I'll setup an
email filter to try and catch iCalendar related subjects, but sometimes
I miss things on the list.
next prev parent reply other threads:[~2024-01-23 6:49 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
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 [this message]
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=87il3ka6jw.fsf@gmail.com \
--to=jackkamm@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hanno@hoowl.se \
--cc=yantar92@gmail.com \
--cc=yantar92@posteo.net \
/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).