Am 26.06.2018 um 11:53 schrieb Nicolas Goaziou: > Hello, > > Tobias Schlemmer <keinstein_jun...@gmx.net> writes: > >> some time ago sent pull request from GitHub to support per-entry >> visibility in iCalendar export. > We don't use GitHub. No problem. I don't remember where I got this advise. Usually I don't send requests to random destinations. >> I attach the patch and some short documentation of the feature in the >> attaced files. They have been updated to honour the timezone patch and >> the documentation switch from texinfo to org-mode. > Applied in "next" branch. Thank you. > > Would you mind providing an entry for ORG-NEWS about it? Attached.
Regards, Tobias
>From 810c66b23aa9302b6a723b257210d97342cebba8 Mon Sep 17 00:00:00 2001 From: Tobias Schlemmer <keinst...@users.sourceforge.net> Date: Tue, 26 Jun 2018 19:47:26 +0200 Subject: [PATCH] Add an entry for iCalendar export CLASS attribute to ORG-NEWS * etc/ORG-NEWS: Document iCalendar export CLASS attribute --- etc/ORG-NEWS | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS index 734732b2b..24f14a097 100644 --- a/etc/ORG-NEWS +++ b/etc/ORG-NEWS @@ -19,6 +19,16 @@ Please send Org bug reports to mailto:emacs-orgmode@gnu.org. See [[git:3367ac9457]] for details. ** New features +*** iCalendar export respects a =CLASS= property +Set the =CLASS= property on an entry to specify a visibility class for +that entry only during iCalendar export. The property can be set to +anything the calendar server supports. The iCalendar standard defines +the values =PUBLIC=, =CONFIDENTIAL=, =PRIVATE=, which can be +interpreted as publicly visable, accessible to a specific group, and +private respectively. + +This property can be inherited during iCalendar export, +depending on the value of ~org-use-property-inheritance~. *** Babel **** Add LaTeX output support in PlantUML *** New parameter for =INCLUDE= keyword -- 2.18.0.rc2