Ihor Radchenko writes:
> Thanks!
> You can replace Maintainer: line in ox-icalendar.el with your name.
Done.
> Sure.
> I checked my records and found one outstanding issue related to
> ox-icalendar -
> https://list.orgmode.org/orgmode/20211230225919.1a660...@hsu-hh.de/
>
> The patch proposed by
Jack Kamm 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 inf
Ihor Radchenko writes:
> Ihor Radchenko 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 (se
Ihor Radchenko 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 wonderin
Hanno Perrey 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 wonde
Greg Sullivan writes:
> I would really like the ability to use the ":myProperty+: " to create
> multi-line properties for the org-export-taskjuggler exporter.
> However, the mentioned patch is quite large and mostly focused on headline
> caching, as far as I can tell.
> @Ihor or @Hanno, Is there
Thank you very much for that suggestion.
Unfortunately, that does not seem to work for org-export-taskjuggler.
An exported taskjuggler file has extremely simple syntax. For a report, for
example, there is the header, "textreport id name {"
then a series of "attribute_name", "value" pairs such as "f
On Mon, Feb 28, 2022 at 3:34 PM Kaushal Modi wrote:
>
> On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey 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-exp
On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey 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 (se
I would really like the ability to use the ":myProperty+: " to create
multi-line properties for the org-export-taskjuggler exporter.
However, the mentioned patch is quite large and mostly focused on headline
caching, as far as I can tell.
@Ihor or @Hanno, Is there a patch just to get the :myPropert
Hanno Perrey 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 wonde
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
intenti
12 matches
Mail list logo
