New Heading Parsing and org-vcard

New Heading Parsing and org-vcard

[Jonas Damm]

Reading here: https://orgmode.org/Changes.html makes me believe breaking
changes in orgmode made the seemingly unmaintained org-vcard package not
work anymore.

> Internal structure of Org parse tree has been changed
> 
> The code relying upon the previously used (TYPE PROPERTIES-PLIST
> CONTENTS-LIST) structure may no longer work. Please use
> org-element-create, org-element-property, and other Org element API
> functions to work with Org syntax trees.
> 
> Some syntax node properties are no longer stored as property list
> elements. Instead, they are kept in a special vector value of a new
> :standard-properties property. This is done to improve performance.
> 
> If there is a need to traverse all the node properties, a new API
> function org-element-properties-map can be used.
> 
> Properties and their values can now be deferred to avoid overheads when
> parsing. They are calculated lazily, when the value/property is
> requested by org-element-property and other getter functions. Using
> plist-get to retrieve values of PROPERTIES-PLIST is not recommended as
> deferred properties will not be resolved in such scenario.
> 
> New special property :secondary is used internally to record which
> properties store secondary objects.
> 
> New special property :deferred is used to keep information how to
> calculate property names lazily.
> 
> See the commentary in lisp/org-element-ast.el for more details.

I tried to modify the org-vcard package, but this is beyond my
capabillities.


So my question is: Can I maybe downgrade orgmode or restore the old
method of parsing some other way? I relied on org-vcard pretty
heavily. I hope I can find a way to keep using it.

Thanks!
Jonas

Re: New Heading Parsing and org-vcard

[Ihor Radchenko]

Jonas Damm <mailing@jonas-damm.de> writes:

> Reading here: https://orgmode.org/Changes.html makes me believe breaking
> changes in orgmode made the seemingly unmaintained org-vcard package not
> work anymore.

AFAIK, org-vcard is maintained at https://github.com/pinoaffe/org-vcard

> So my question is: Can I maybe downgrade orgmode or restore the old
> method of parsing some other way? I relied on org-vcard pretty
> heavily. I hope I can find a way to keep using it.

It might be enough to replace plist-get with org-element-property calls.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
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>

Re: New Heading Parsing and org-vcard

[Jonas Damm]

I tried that already, it did not work. I tried using the debugging but
the I could not understand the output.
Ihor Radchenko <yantar92@posteo.net> writes:

> Jonas Damm <mailing@jonas-damm.de> writes:
>
>> Reading here: https://orgmode.org/Changes.html makes me believe breaking
>> changes in orgmode made the seemingly unmaintained org-vcard package not
>> work anymore.
>
> AFAIK, org-vcard is maintained at https://github.com/pinoaffe/org-vcard
>
>> So my question is: Can I maybe downgrade orgmode or restore the old
>> method of parsing some other way? I relied on org-vcard pretty
>> heavily. I hope I can find a way to keep using it.
>
> It might be enough to replace plist-get with org-element-property calls.

Re: New Heading Parsing and org-vcard

[Ihor Radchenko]

Jonas Damm <mailing@jonas-damm.de> writes:

> I tried that already, it did not work. I tried using the debugging but
> the I could not understand the output.

Then, you can share your debugging results, so that we have a chance to help.

Or, indeed, you can come back to earlier version of Org mode.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
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>

Re: New Heading Parsing and org-vcard

[resource1]

I lost org-vcard functionality too when I last upgraded 
org-mode.

I've been using the export function built in to org-contacts 
in the meantime, but it's pretty bare bones.

Given the number of people who try and live in Emacs I'm 
surprise the loss of contact support hasn't impacted more 
users. Would be great to get this working again.