From: Bastien Guerry <bzg@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: "Thomas S. Dye" <tsd@tsdye.online>,
Ihor Radchenko <yantar92@posteo.net>,
emacs-orgmode@gnu.org
Subject: Re: [PATCH] doc/org-manual.org (Summary): Clarify the Org markup is human-readable
Date: Wed, 03 Jan 2024 13:36:27 +0100 [thread overview]
Message-ID: <87edeya910.fsf@bzg.fr> (raw)
In-Reply-To: <ZZUSMoCAtoqsq5XV@lco.syogm.com> (Jean Louis's message of "Wed, 3 Jan 2024 10:52:18 +0300")
Jean Louis <bugs@gnu.support> writes:
> It's primary use was for Emacs users to make notes, TODO tasks,
> etc. It is secondary that it became leightweight markup language that
> can export to various documents.
IMHO it has always been a _lightweight markup language_, used for
notes and TODO tasks, then soon enough for exporting too.
I got interested to Org back circa 2006 after I stopped working on a
small library called bhl.el: https://www.nongnu.org/bhl/
BHL was a lightweight markup language targetting export only. Org was
vastly superior in all accounts, so I contributed to Org.
--
Bastien Guerry
next prev parent reply other threads:[~2024-01-03 12:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 15:24 [PATCH] doc/org-manual.org (Summary): Clarify the Org markup is human-readable Ihor Radchenko
2024-01-02 5:24 ` Thomas S. Dye
2024-01-03 7:52 ` Jean Louis
2024-01-03 12:36 ` Bastien Guerry [this message]
2024-01-03 13:00 ` Ihor Radchenko
2024-01-02 22:47 ` Matt
2024-01-03 13:44 ` Comments on Summary section of Org manual (was: [PATCH] doc/org-manual.org (Summary): Clarify the Org markup is human-readable) Ihor Radchenko
2024-01-03 20:43 ` Matt
2024-01-05 13:17 ` Ihor Radchenko
2024-01-05 13:06 ` [PATCH v2] doc/org-manual.org (Summary): Clarify the Org markup is human-readable Ihor Radchenko
2024-01-06 10:31 ` Matt
2024-01-06 12:55 ` Ihor Radchenko
2024-01-06 12:56 ` Matt
2024-02-01 12:16 ` Ihor Radchenko
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=87edeya910.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.online \
--cc=yantar92@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).