From: Leo Vivier <zaeph@zaeph.net>
To: Bastien <bzg@gnu.org>
Cc: hj-orgmode-1@hj.proberto.com,
Wes Hardaker <wjhns209@hardakers.net>,
emacs-orgmode@gnu.org, Palak Mathur <palakmathur@gmail.com>,
TEC <tecosaur@gmail.com>
Subject: Re: Shower thought: submit an IETF RFC to register Org as a MIME type
Date: Sat, 24 Oct 2020 15:09:07 +0200 [thread overview]
Message-ID: <87zh4bixe4.fsf@hidden> (raw)
In-Reply-To: <87ft63hjoh.fsf@bzg.fr>
Hi there,
Bastien <bzg@gnu.org> writes:
> As the first paragraph says:
>
> "This document describes and comments Org syntax as it is currently
> read by its parser (Org Elements)"
>
> while we need a description of Org's syntax from the point of view of
> (1) a human writer and (2) any possible Org parser.
I agree that (1) and (2) should be two different documents. (2) would
be especially interesting since there are quite a few projects afoot to
parse Org documents outside of Emacs:
- go-org (Go)
https://github.com/niklasfasching/go-org
- orgize (Rust)
https://docs.rs/orgize/0.8.4/orgize/
They are in various stages of advancement, but a design document would
go a long way in federating those efforts.
> I don't know how difficult it is, but I suspect it is quite a lot of
> work.
I assume that it would be, yes. However, as someone with a vested
interest in developing an efficient external parser for Org documents,
I’d love to contribute. I’ve been playing around lately with ox.el to
write an exporter to Jupyter (more on that soon), and since it makes
extensive use of org-element.el, I’d have a modicum of knowledge upon
which I could initiate the effort.
Best,
--
Leo Vivier
Freelance Software Engineer
Website: www.leovivier.com | Blog: www.zaeph.net
next prev parent reply other threads:[~2020-10-24 13:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 14:44 TEC
2020-09-04 16:14 ` Gustav Wikström
2020-09-05 5:30 ` stardiviner
2020-09-05 5:50 ` Bastien
2020-09-05 5:53 ` TEC
2020-09-17 7:09 ` TEC
2020-09-17 7:18 ` hj-orgmode-1
2020-09-23 7:31 ` Bastien
2020-10-01 3:40 ` TEC
2020-10-01 5:21 ` Bastien
2020-10-01 5:48 ` TEC
2020-10-01 6:46 ` Bastien
2020-10-01 15:39 ` Wes Hardaker
2020-10-01 15:45 ` TEC
2020-10-06 18:03 ` Wes Hardaker
2020-10-06 19:03 ` TEC
2020-10-06 20:39 ` Palak Mathur
2020-10-24 12:09 ` Bastien
2020-10-24 12:28 ` Palak Mathur
2020-10-24 12:50 ` Bastien
2020-10-24 13:09 ` Leo Vivier [this message]
2020-10-24 13:38 ` Bastien
2020-10-24 13:49 ` Leo Vivier
2020-10-24 15:12 ` Bastien
2020-10-24 15:00 ` Palak Mathur
2020-10-24 15:40 ` Bastien
2020-10-24 15:57 ` Palak Mathur
2020-10-14 9:52 ` Lennart C. Karssen
2020-10-14 14:22 ` Nicolas Goaziou
2021-03-23 3:00 ` Timothy
2020-09-24 20:25 Andrea
2020-09-24 20:25 Andrea
2021-10-22 1:21 Carlos Pita
2021-10-23 6:45 ` Ihor Radchenko
2021-10-23 8:34 ` Carlos Pita
2021-10-23 8:36 ` Timothy
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh4bixe4.fsf@hidden \
--to=zaeph@zaeph.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=hj-orgmode-1@hj.proberto.com \
--cc=palakmathur@gmail.com \
--cc=tecosaur@gmail.com \
--cc=wjhns209@hardakers.net \
--subject='Re: Shower thought: submit an IETF RFC to register Org as a MIME type' \
/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
Code repositories for project(s) associated with this inbox:
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).