emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Ashton <data@gtf.org>
To: emacs-orgmode@gnu.org
Subject: Re: "Orgdown", the new name for the syntax of Org-mode
Date: Sun, 28 Nov 2021 18:33:03 -0800	[thread overview]
Message-ID: <16F7037A-6055-4500-AE04-72DAC60DBA8E@gtf.org> (raw)
In-Reply-To: <75ce32ea-616b-0293-1eb5-f9b64afd42ed@gmail.com>


> On Nov 28, 2021, at 6:22 PM, Jim Porter <jporterbugs@gmail.com> wrote:
> 
> On 11/28/2021 11:46 AM, Karl Voit wrote:
>> At this year's EmascsConf, I had a 12 minute video where I explain why
>> we do need a different name for the syntax of Org-mode in contrast to
>> the Elisp implementation of GNU/Emacs Org-mode.
>> I would like you to read my rationale and motivate you to use the term
>> "Orgdown" for the syntax and "Orgdown1" for the first (very basic)
>> level of Orgdown syntax elements.
> 
> I agree that it's useful to distinguish the files/syntax from the *mode*, which contains many functions for doing things with those files.
> 
> For what it's worth (perhaps not much), I've always referred to the syntax/file format as simply "Org"; for example, "I put my notes into an Org file." This is by analogy with most of the other Emacs major modes for editing files. I write Python in `python-mode', I write C++ in `c++-mode', I write text files in `text-mode', and so on.
> 
> Maybe "Org" isn't distinct enough though. People unfamiliar with Org-Mode might confuse "Org" with "org charts" or some other use of the word. Still, if we look to other tools that can read the same files as Org-Mode, they tend to be called things like "Organice", not "Orgmodeanice". :)

Perhaps orgtext or org-text?



  reply	other threads:[~2021-11-29  2: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
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 [this message]
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=16F7037A-6055-4500-AE04-72DAC60DBA8E@gtf.org \
    --to=data@gtf.org \
    --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).