From: "M. ‘quintus’ Gülker" <mg@guelker.eu>
To: emacs-orgmode@gnu.org
Subject: Re: "Orgdown", the new name for the syntax of Org-mode
Date: Mon, 29 Nov 2021 19:27:18 +0100 [thread overview]
Message-ID: <87tufuu8ah.fsf@atlantis> (raw)
In-Reply-To: <2021-11-29T14-12-55@devnull.Karl-Voit.at>
Am Montag, dem 29. November 2021 schrieb Karl Voit:
> It seems to be the case that the name "Orgdown" is the reason why
> the Org-mode community does not support the idea of an
> implementation-agnostic definition of the syntax. Which is ... kinda
> funny if you think about it.
>
> Well if the project is not working out, at least I made my point and
> we continue to have all those misunderstandings and lack of Orgdown
> support in 3rd party tools (because Org-mode is way too big).
I think the project has value; better tooling outside of Emacs is
something org can only profit from in my opinion. One point that has not
been raised yet are scenarios of collaborative work; I would enjoy it
quite a bit if I could work on documents together with people who do not
like Emacs as an editor for whatever reason. Currently, org as a file
format is pretty much excluded if collaboration is intended with someone
who does not use Emacs. The natural choice in these cases is Markdown.
I agree that the name is kind of odd as it seems as if it is necessary
to invoke some association to Markdown. Other markup languages also do
not need that -- Textile, Asciidoc, etc. Perhaps it is best to simply
ignore the naming issue and focus on the actual work instead. It is far
more important to get the compatibility levels defined. After that you
can still reconsider the naming.
> Oh, there is a very large danger here of getting something that is
> not compatible with Org-mode any more. I don't think that this would
> be a good thing. At least the different flavors killed the fun of
> Markdown for me.
The astonishing thing is that most people manage to get along despite of
the incompatibilities of the different Markdown flavours. Otherwise
Markdown would not be such a success. Why is this? What can be learned
from this for creating org tools outside of Emacs? Actually surveying
this might be of interest.
Maybe most documents are very simple files. README files for FLOSS
projects, forum posts, blog posts. For such content the features where
the Markdown implementations differ are usually not required. It
suffices to use unstyled text, headings, code blocks, quotes, emphasis.
That is it basically. org shines on documents where more is required --
documentation, books, since recently scientific articles. Markdown’s
common subset is not expressive enough for these documents, whereas for
simple documents there is not much benefit in trading in Markdown for
org. Thus, maybe it is more fruitful to try to market org(down) as a
markup for complex documents, with the added benefit that it does
incidentally also cover simple documents nicely on par with Markdown.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kontakt@guelker.eu | O<
next prev parent reply other threads:[~2021-11-29 18:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 19:46 "Orgdown", the new name for the syntax of Org-mode Karl Voit
2021-11-28 21:34 ` Jean-Christophe Helary
2021-11-28 21:39 ` Bruce D'Arcus
2021-11-28 21:50 ` Tom Gillespie
2021-11-28 22:25 ` Juan Manuel Macías
2021-11-28 22:57 ` Tom Gillespie
2021-11-28 23:16 ` Joost Kremers
2021-11-29 1:36 ` George Mauer
2021-11-29 3:25 ` Juan Manuel Macías
2021-11-29 7:13 ` Dr. Arne Babenhauserheide
2021-11-28 23:24 ` Jean-Christophe Helary
2021-11-29 3:25 ` Devin Prater
2021-12-26 14:54 ` Jean-Christophe Helary
2021-11-29 5:41 ` Marcin Borkowski
2021-11-29 12:18 ` Juan Manuel Macías
2021-11-29 12:36 ` Marcin Borkowski
2021-11-28 22:42 ` Tim Cross
2021-11-29 13:19 ` Karl Voit
2021-11-29 15:12 ` Matt Price
2021-11-29 18:27 ` M. ‘quintus’ Gülker [this message]
2021-11-30 7:39 ` Marcin Borkowski
2021-11-30 20:44 ` Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode) Karl Voit
2021-11-30 22:28 ` Dr. Arne Babenhauserheide
2021-11-30 22:50 ` Eduardo Ochs
2021-12-01 0:41 ` Tom Gillespie
2021-12-01 1:12 ` Tim Cross
2021-12-01 3:28 ` Orgdown: negative feedback & attempt of a root-cause analysis Juan Manuel Macías
2021-12-01 21:17 ` Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode) M. ‘quintus’ Gülker
2021-12-02 6:50 ` Orgdown: negative feedback & attempt of a root-cause analysis Eric S Fraga
2021-12-01 23:43 ` Karl Voit
2021-12-02 1:44 ` Tim Cross
2021-12-02 2:12 ` George Mauer
2021-12-02 8:07 ` Greg Minshall
2021-11-29 2:22 ` "Orgdown", the new name for the syntax of Org-mode Jim Porter
2021-11-29 2:33 ` Michael Ashton
2021-11-29 12:38 ` Max Nikulin
2021-11-29 12:58 ` Christophe Schockaert
2021-11-30 23:50 ` Samuel Wales
2021-11-30 23:56 ` Samuel Wales
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=87tufuu8ah.fsf@atlantis \
--to=mg@guelker.eu \
--cc=emacs-orgmode@gnu.org \
/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).