From: Devin Prater <r.d.t.prater@gmail.com>
To: Jean-Christophe Helary <lists@traduction-libre.org>
Cc: "Juan Manuel Macías" <maciaschain@posteo.net>,
"Tom Gillespie" <tgbugs@gmail.com>,
orgmode <emacs-orgmode@gnu.org>
Subject: Re: "Orgdown", the new name for the syntax of Org-mode
Date: Sun, 28 Nov 2021 21:25:25 -0600 [thread overview]
Message-ID: <CAGJxbF7zT4Sw2Yf-+iwo_UDDzOCp5kVWLtvACc-EkfAZrcnwgQ@mail.gmail.com> (raw)
In-Reply-To: <4424C113-509F-474F-9D73-0FA6B2BED13D@traduction-libre.org>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Or OrgMark. Simple, please no levels to show the amount of adherence to the
spec. OrgMark would symbolize the "markings" or syntax of Org-mode, and not
be close enough to Mark(down) to where people would think, like I did, that
this was Org-mode power given to a subset of Markdown to help, say,
Obsidian users come to Org-mode. No, I don't think we need that either.
Otherwise, I'm perfectly find with calling it Org. Just like Python, HTML,
all that. We don't say, in relaxed speech where the speaker assumes prior
known knowledge, or knowledge that can be easily filled in, "I'm writing a
book in Markdown markup language." We just say "I'm writing a book in
Markdown." And if the listener doesn't know what we mean, we can explain.
Devin Prater
r.d.t.prater@gmail.com
On Sun, Nov 28, 2021 at 5:24 PM Jean-Christophe Helary <
lists@traduction-libre.org> wrote:
>
>
> > On Nov 29, 2021, at 7:57, Tom Gillespie <tgbugs@gmail.com> wrote:
> >
> > PS Another brainstormed name: Orgsyn?
>
> Org Agnostic Syntax Modules → OrgASM
>
> --
> Jean-Christophe Helary @brandelune
> https://mac4translators.blogspot.com
> https://sr.ht/~brandelune/omegat-as-a-book/
>
>
>
[-- Attachment #2: Type: text/html, Size: 2091 bytes --]
next prev parent reply other threads:[~2021-11-29 3:59 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 [this message]
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=CAGJxbF7zT4Sw2Yf-+iwo_UDDzOCp5kVWLtvACc-EkfAZrcnwgQ@mail.gmail.com \
--to=r.d.t.prater@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lists@traduction-libre.org \
--cc=maciaschain@posteo.net \
--cc=tgbugs@gmail.com \
/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).