From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: stefankangas@gmail.com, rms@gnu.org, philipk@posteo.net,
hanno@hoowl.se, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: jami-bot and org-jami-bot
Date: Fri, 12 Jan 2024 16:37:25 +0200 [thread overview]
Message-ID: <83ply6ipne.fsf@gnu.org> (raw)
In-Reply-To: <87il3yprkx.fsf@localhost> (message from Ihor Radchenko on Fri, 12 Jan 2024 14:13:50 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: stefankangas@gmail.com, rms@gnu.org, philipk@posteo.net, hanno@hoowl.se,
> emacs-devel@gnu.org
> Date: Fri, 12 Jan 2024 14:13:50 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> If someone writes a parser that can understand alternative, non-Org
> >> markup of source files, and produce org-element-ast.el-compatible list
> >> structure, most of the ox-* exporters should remain functional.
> >
> > It would be better to allow alternative data structures to be input to
> > the export functionality, rather than expect other features to mimic
> > the Org parser and its outputs.
>
> One way or another, there should be some structure to the parser output.
> Org parser output is just a nested list.
> org-element-ast.el defines the details of what can be inside that list -
> independent of the details of Org markup, and compatible with the
> existing ox-* implementations.
I don't see org-element-ast.el in the Emacs tree, so I cannot see what
kind of structures it defines.
next prev parent reply other threads:[~2024-01-12 14:37 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 11:21 [ELPA] New package: jami-bot and org-jami-bot Hanno Perrey
2023-12-28 21:33 ` Stefan Kangas
2023-12-29 14:08 ` Hanno Perrey
2023-12-30 3:20 ` Richard Stallman
2023-12-30 10:29 ` Hanno Perrey
2024-01-01 3:34 ` Richard Stallman
2023-12-30 12:15 ` [DISCUSSION] Possible inclusion of org-capture.el into Emacs core (was: [ELPA] New package: jami-bot and org-jami-bot) Ihor Radchenko
2023-12-30 17:43 ` Stefan Kangas
2024-01-01 3:34 ` Richard Stallman
2024-01-01 3:59 ` Richard Stallman
2024-01-01 14:05 ` Ihor Radchenko
2023-12-30 12:43 ` [DISCUSSION] org-capture.el vs remember.el " Ihor Radchenko
2023-12-30 17:20 ` Stefan Kangas
2023-12-30 19:16 ` João Távora
2023-12-30 19:19 ` João Távora
2023-12-31 18:05 ` Adam Porter
2024-01-07 21:01 ` [ELPA] New package: jami-bot and org-jami-bot Stefan Kangas
2024-01-08 21:08 ` Richard Stallman
2024-01-08 21:29 ` Ihor Radchenko
2024-01-09 3:30 ` Eli Zaretskii
2024-01-09 4:42 ` Stefan Kangas
2024-01-10 4:24 ` Richard Stallman
2024-01-10 5:36 ` Stefan Kangas
2024-01-10 4:24 ` Richard Stallman
2024-01-11 15:30 ` ELPA packages and Org mode integration (was: [ELPA] New package: jami-bot and org-jami-bot) Ihor Radchenko
2024-01-09 19:39 ` [ELPA] New package: jami-bot and org-jami-bot Philip Kaludercic
2024-01-11 18:51 ` Richard Stallman
2024-01-11 20:12 ` Stefan Kangas
2024-01-12 7:24 ` Eli Zaretskii
2024-01-12 12:38 ` Ihor Radchenko
2024-01-12 13:59 ` Eli Zaretskii
2024-01-12 14:13 ` Ihor Radchenko
2024-01-12 14:37 ` Eli Zaretskii [this message]
2024-01-12 14:45 ` Ihor Radchenko
2024-01-12 15:04 ` Eli Zaretskii
2024-01-12 15:17 ` Ihor Radchenko
2024-01-14 3:03 ` Richard Stallman
2024-01-14 3:03 ` Richard Stallman
2024-01-14 9:58 ` Stefan Kangas
2024-01-14 10:25 ` Emanuel Berg
2024-01-14 11:43 ` Ihor Radchenko
2024-01-14 10:47 ` Emanuel Berg
2024-01-17 3:29 ` Richard Stallman
2024-01-31 3:34 ` Richard Stallman
2024-02-03 9:28 ` Hanno Perrey
2024-01-15 3:12 ` Richard Stallman
2024-01-12 15:04 ` Hanno Perrey
2024-01-16 3:31 ` Richard Stallman
2024-01-17 8:00 ` Hanno Perrey
2024-01-12 14:58 ` Hanno Perrey
2024-01-14 18:46 ` Hanno Perrey
2024-01-15 7:06 ` Philip Kaludercic
2024-01-17 7:59 ` Hanno Perrey
2024-01-17 23:39 ` Philip Kaludercic
2024-01-20 14:46 ` Hanno Perrey
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=83ply6ipne.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hanno@hoowl.se \
--cc=philipk@posteo.net \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
--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).