From: Richard Lawrence <rwl@recursewithless.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Improving Emacs' iCalendar support
Date: Fri, 25 Oct 2024 14:53:19 +0200 [thread overview]
Message-ID: <878qucxs1s.fsf@ohm.mail-host-address-is-not-set> (raw)
In-Reply-To: <875xpho0nu.fsf@localhost>
Hi Ihor,
Ihor Radchenko <yantar92@posteo.net> writes:
> Richard Lawrence <rwl@recursewithless.net> writes:
>
>>> While I started extending the gnus-icalendar-event EIEIO class to
>>> support property parameters, it ended up being very cumbersome to
>>> create new event objects with all parameters correctly set.
>
> As an alternative option, you may consider using org-element-ast API -
> it is a generic data structure and API that Org mode uses to handle
> parsed AST. It is servility optimized for performance and does not
> really depend on other parts of Org mode.
Thanks for pointing me to this! I took a look at the file commentary,
and I've played around with org-element before. I do like org-element's
plist-based format...it makes things simple and readable as an outside
tinkerer.
Can you tell me a bit more about the performance benefits? Do these
mostly just stem from the use of an array for :standard-properties?
(You get this for free with cl-structs, too.) Or is it more about when
and how parsing happens? (This is something I feel like I've never
grasped in org-element...in the past I've been confused because the
properties I'd see when calling e.g. org-element-at-point would be
different than the ones available in some other context.)
Thanks!
Best,
Richard
next prev parent reply other threads:[~2024-10-25 12:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 9:01 Improving Emacs' iCalendar support Richard Lawrence
2024-10-18 9:24 ` Eli Zaretskii
2024-10-19 8:22 ` Richard Lawrence
2024-10-19 10:11 ` Eli Zaretskii
2024-10-20 5:08 ` Richard Lawrence
2024-10-20 5:21 ` Eli Zaretskii
2024-10-18 12:58 ` Sebastián Monía
2024-10-19 8:28 ` Richard Lawrence
2024-10-19 5:44 ` Adam Porter
2024-10-19 8:39 ` Richard Lawrence
2024-10-20 3:09 ` Adam Porter
2024-10-22 18:40 ` Ihor Radchenko
2024-10-23 7:29 ` Björn Bidar
2024-10-23 9:01 ` Richard Lawrence
2024-10-23 20:24 ` Ferdinand Pieper
2024-10-24 14:52 ` Richard Lawrence
2024-10-24 17:45 ` Ihor Radchenko
2024-10-25 12:53 ` Richard Lawrence [this message]
2024-10-25 18:59 ` Ihor Radchenko
[not found] ` <87plnr6zvk.fsf@>
2024-10-23 8:09 ` Ihor Radchenko
2024-10-23 9:05 ` Richard Lawrence
2024-10-23 10:03 ` Björn Bidar
2024-10-21 6:10 ` Björn Bidar
2024-10-21 6:22 ` Visuwesh
2024-10-23 9:15 ` Richard Lawrence
2024-10-23 9:45 ` Visuwesh
[not found] ` <87wmi29eaf.fsf@>
2024-10-26 17:49 ` Ihor Radchenko
2024-10-28 10:44 ` Björn Bidar
[not found] ` <87r080tslf.fsf@>
2024-10-28 19:09 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878qucxs1s.fsf@ohm.mail-host-address-is-not-set \
--to=rwl@recursewithless.net \
--cc=emacs-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.