From: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: "Orgdown", the new name for the syntax of Org-mode
Date: Mon, 29 Nov 2021 10:12:46 -0500 [thread overview]
Message-ID: <CAN_Dec_D7=Uh0+kA7X8u=EpCsNgFEfYnyMrUpBq7bBK=D=y1nA@mail.gmail.com> (raw)
In-Reply-To: <2021-11-29T14-12-55@devnull.Karl-Voit.at>
[-- Attachment #1: Type: text/plain, Size: 3650 bytes --]
I don't have very thoughtful comments but I'll just say that I really do
also like the idea of a formal syntax; that a staged standard seems to make
sense to me, though I'm ignorant about how syntaxes are normally defined
and managed; and am generally not super enthusiastic about the particular
name that's been chosen.
It seems like there are lots of people thinking in similar ways about
related issues -- that is, whenever it's possible, treating org files as
syntax trees rather than linear text trees.. The org-ml project comes to
mind; so does the recent work on tree-sitter in emacs; and Ihor's recent
thread on changing fontification. I guess it would be nice if the
smarter-than-me people involved in all these projects are tracking each
other somewhat to make sure efforts converge as much as possible.
For me it would be really great to have better support for an org syntax in
VSCode & in Node; I'm sure other people have their own priority areas. A
syntax definition would surely help?
On Mon, Nov 29, 2021 at 8:22 AM Karl Voit <devnull@karl-voit.at> wrote:
> Hi Tim,
>
> * Tim Cross <theophilusx@gmail.com> wrote:
> >
> > Hi Karl,
> >
> > while I can appreciate the point you are making, I'm doubtful your
> > suggestion will gain the traction necessary to work.
>
> You might be right. Only time will tell. ;-)
>
> > To me, it feels a little like the frequent posts from RMS in the
> > emacs-devel list where he gets upset when people refer to Linux
> > instead of GNU Linux.
>
> I disagree here.
>
> Linux vs. GNU/Linux are two different names for the same thing.
> Org-mode is an Elisp implementation and Orgdown is just a syntax
> definition. So they are completely different things.
>
> > To some extent, the distinction will be too subtle for many and
> > often, it isn't clear whether an issue is a syntax definition
> > (orgdown) or an implementation bug or just simply user
> > misunderstanding.
>
> 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).
>
> > Perhaps we just need a name for the markup syntax which doesn't actually
> > reference 'org' at all - it simply is the markup syntax which org
> > happens to use. A completely separate name might avoid confusion and
> > would make it very clear that the markup syntax is not org mode. Problem
> > is, naming is terribly difficult and I have no suggestions on what would
> > be a good name.
>
> 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.
>
> > I have not yet viewed your video, but will certainly be doing so. Again,
> > agree with the sentiment of what your trying to do, just not convinced
> > it is compatible with basic human nature.
>
> Maybe we need to differ between the Org-mode community with
> potential bias and the main target group of people who did use
> Markdown in the past and never have heard of Org-mode before?
>
> --
> get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
> > get Memacs from https://github.com/novoid/Memacs <
> Personal Information Management > http://Karl-Voit.at/tags/pim/
> Emacs-related > http://Karl-Voit.at/tags/emacs/
>
>
>
[-- Attachment #2: Type: text/html, Size: 4659 bytes --]
next prev parent reply other threads:[~2021-11-29 15:33 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 [this message]
2021-11-29 18:27 ` M. ‘quintus’ Gülker
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='CAN_Dec_D7=Uh0+kA7X8u=EpCsNgFEfYnyMrUpBq7bBK=D=y1nA@mail.gmail.com' \
--to=moptop99@gmail.com \
--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).