emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Jack Kamm <jackkamm@gmail.com>
Cc: Ihor Radchenko <yantar92@gmail.com>,
	Hanno Perrey <hanno@hoowl.se>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inconsistent handling of multi-line properties
Date: Thu, 25 Jan 2024 13:35:35 +0000	[thread overview]
Message-ID: <87fryllemw.fsf@localhost> (raw)
In-Reply-To: <87il3ka6jw.fsf@gmail.com>

Jack Kamm <jackkamm@gmail.com> writes:

>>> 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.

Done.
Fixed, on main. 
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8ec89c53c

>> 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 :)

Thanks!
You can replace Maintainer: line in ox-icalendar.el with your name.
(Nicolas informed me that he no longer maintains Org mode libraries)

> 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.

Sure.
I checked my records and found one outstanding issue related to
ox-icalendar -
https://list.orgmode.org/orgmode/20211230225919.1a660666@hsu-hh.de/

The patch proposed by Detlef still has outstanding issues to address,
but the author does not have free time to work on this since the
beginning of last year (I did several follow-ups off list; latest in
September).

At this point, we should either cancel that patch or amend it ourselves
and apply.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-01-25 13:32 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
2024-01-25 13:35       ` Ihor Radchenko [this message]
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=87fryllemw.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=hanno@hoowl.se \
    --cc=jackkamm@gmail.com \
    --cc=yantar92@gmail.com \
    /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).