From: Bastien <bzg@gnu.org>
To: Timothy <orgmode@tec.tecosaur.net>
Cc: Karl Voit <news2042@Karl-Voit.at>,
Karl Voit <devnull@Karl-Voit.at>,
emacs-orgmode@gnu.org
Subject: Re: Org-mode syntax as a tool-independent MIME type
Date: Tue, 18 Oct 2022 09:22:38 +0200 [thread overview]
Message-ID: <87fsfl7g01.fsf@bzg.fr> (raw)
In-Reply-To: <87y1tdvppg.fsf@tec.tecosaur.net> (Timothy's message of "Tue, 18 Oct 2022 09:55:20 +0800")
Hi Karl and Timothy,
thank you Karl for reviving this important topic.
I think our collective priority should be to work on
https://orgmode.org/worg/dev/org-synxtax.html so that it reflects the
current Org syntax. Hopefully we can do this before Org 9.6. As
discussed with TEC, we can factor out suggestions from this document
so that it is not a mix of facts and hypotheses.
Then we can work on suggestions for evolutions of the current Org-mode
syntax chunk by chunk, as a long-term goal for stabilizing changes for
Org 10 (2023 ?)
What occurred to me while rereading this thread is that definining a
syntax for a IETF RFC on an Org mimetype probably needs to be done not
just by this Emacs Org-mode community, but by bringing together other
"consumers" of .org files, from ecosystems outside of Emacs.
Such a collective work could lead to define what subset of the Org
syntax is useful as the corner-stone for .org files everywhere - which
is what you rightfully brought up with "Orgdown".
If successful, such a process could end up in defining the minimal and
official "Org syntax" while allowing implementations (like the one for
Emacs org-mode) to supercharge this syntax if deemed useful.
Perhaps TEC is right and we will end up having the minimal syntax
being the one we currently use for Org-mode: we'll see.
But we need volunteers: one to work on worg/dev/org-synxtax.org (I'm
assuming TEC can lead the work here) and one to set up a discussion
with people implementing Org in various places (you ?).
I suggest to take this sequentially and not tackle the second work
before we're done with the first one.
2 cts,
--
Bastien
next prev parent reply other threads:[~2022-10-18 7:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 14:44 Shower thought: submit an IETF RFC to register Org as a MIME type 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
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
2022-10-17 20:46 ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Karl Voit
2022-10-18 1:55 ` Timothy
2022-10-18 7:22 ` Bastien [this message]
2022-10-18 8:13 ` Org-mode syntax as a tool-independent MIME type Karl Voit
2022-10-21 11:44 ` Ihor Radchenko
2022-10-18 8:05 ` Karl Voit
2022-10-21 11:41 ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Ihor Radchenko
2021-03-23 3:00 ` Shower thought: submit an IETF RFC to register Org as a MIME type 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=87fsfl7g01.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=devnull@Karl-Voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news2042@Karl-Voit.at \
--cc=orgmode@tec.tecosaur.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/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).