From: Ihor Radchenko <yantar92@posteo.net>
To: Jean Louis <bugs@gnu.support>
Cc: "Thomas S. Dye" <tsd@tsdye.online>, Bastien <bzg@gnu.org>,
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:00:29 +0000 [thread overview]
Message-ID: <87r0iya7wy.fsf@localhost> (raw)
In-Reply-To: <ZZUSMoCAtoqsq5XV@lco.syogm.com>
Jean Louis <bugs@gnu.support> writes:
> In my opinion, it's not that Org was intentionally designed to be
> "lightweight markup readable for humans"; rather, it was maintained in
> a manner that focused on preserving its readability and prevented it
> from evolving into something less comprehensible.
The point of my patch is not to show history of Org markup. Rather to
guide the future direction - if we ever add new or change the existing
Org syntax, readability is one of the design guidelines we should follow
(IMHO). Stating it explicitly in the manual will make this guidelines
explicit.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-03 12:58 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
2024-01-03 13:00 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0iya7wy.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bugs@gnu.support \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.online \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.