emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: Joost Kremers <joostkremers@fastmail.fm>, emacs-orgmode@gnu.org
Subject: Re: "Orgdown", the new name for the syntax of Org-mode
Date: Mon, 29 Nov 2021 08:13:53 +0100	[thread overview]
Message-ID: <87czmj77e7.fsf@web.de> (raw)
In-Reply-To: <87r1azskw5.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]


Juan Manuel Macías <maciaschain@posteo.net> writes:

> Joost Kremers writes:
>
>> Why not just use the term "Org markup"?  It's descriptive and should be
>> understandable to people familiar with the concept of markup languages.
>
> This. 'Org markup language' and 'Org Syntax' are obvious and natural
> terms that can easily be inferred from the Org manual. Honestly I don't
> see much point in coming up with new names for a concept which is
> already transparent and self-explanatory. It is something I find
> unnecessary and baroque.

Org markup and Org syntax sound good, I think. I’m unsure which is
better to convey that this includes features — that org-mode is much
more than just a way to encode some information, but a way to interact
with documents and an implementation of the syntax should keep that in
mind.

One thing that is important to keep: Org Syntax or Org Markup is
implementation-defined. You cannot claim *full compatibility*, if you
are not fully compatible with org-mode. This includes a lot of Emacs
features, like linking to arbitrary files/buffers/things, extending
links, and so on.

The minimal syntax (missing a lot of features) would be outline markup
or outline syntax (from outline-mode, the ancestor of org-mode).

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2021-11-29  7:24 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 [this message]
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
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=87czmj77e7.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=joostkremers@fastmail.fm \
    --cc=maciaschain@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/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).