From: Richard Lawrence <rwl@recursewithless.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: Re: Improving Emacs' iCalendar support
Date: Mon, 25 Nov 2024 10:09:15 +0100 [thread overview]
Message-ID: <87jzcraddw.fsf@ohm.mail-host-address-is-not-set> (raw)
In-Reply-To: <86ed31j6zk.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> 1) The basic form of the syntax tree is based on the format of the Org
>> parse tree in org-element-ast.el (though for now I have not implemented
>> any of the performance optimizations). Syntax nodes are a four-element
>> list of a type symbol, a metadata structure, a value, and a list of
>> children. Type symbols are used to store metadata about all the
>> iCalendar grammar categories and to do type-based dispatch in the
>> parser.
>
> Since iCalendar is not tightly coupled to Org, it would be best not to
> load Org for supporting iCalendar features.
Sorry if I was unclear: I'm not loading org-element-ast.el or using it
directly; I have just adopted the same basic format for iCalendar syntax
nodes. This should make it easier to switch to org-element-ast.el
if/when it eventually becomes a more generalized library. But at the
moment, there are enough feature differences that I don't think that
makes sense.
> Is it possible to use peg.el instead?
I was not aware of peg.el, and it doesn't seem to be installed in my
(Debian-built) Emacs -- find-library does not find it. Is it new? Where
can I take a look at it?
Best,
Richard
next prev parent reply other threads:[~2024-11-25 9:09 UTC|newest]
Thread overview: 52+ 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
[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-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
2024-10-25 18:59 ` Ihor Radchenko
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
2024-11-23 8:44 ` Richard Lawrence
2024-11-24 9:50 ` Eli Zaretskii
2024-11-24 10:21 ` Ihor Radchenko
2024-11-24 10:41 ` Eli Zaretskii
2024-11-24 10:58 ` Ihor Radchenko
2024-11-24 11:08 ` Eli Zaretskii
2024-11-24 11:21 ` Upstreaming org-element-ast (was: Improving Emacs' iCalendar support) Ihor Radchenko
2024-11-24 12:55 ` Eli Zaretskii
2024-12-25 11:31 ` Ihor Radchenko
2024-12-29 20:19 ` Richard Lawrence
2024-12-29 20:53 ` Richard Lawrence
2024-12-30 17:18 ` Ihor Radchenko
2024-12-30 17:16 ` bug#74994: " Ihor Radchenko
2024-12-31 7:55 ` Richard Lawrence
2025-01-01 9:29 ` Ihor Radchenko
2025-01-01 12:38 ` Richard Lawrence
2025-01-01 13:01 ` Richard Lawrence
2024-11-25 9:09 ` Richard Lawrence [this message]
2024-11-25 12:42 ` Improving Emacs' iCalendar support Eli Zaretskii
2024-11-25 13:03 ` Rudolf Schlatte
2024-11-25 13:36 ` Eli Zaretskii
2024-11-25 17:14 ` Richard Lawrence
2024-12-20 13:21 ` Richard Lawrence
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzcraddw.fsf@ohm.mail-host-address-is-not-set \
--to=rwl@recursewithless.net \
--cc=eliz@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).