emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: Ihor Radchenko <yantar92@posteo.net>, 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, 3 Jan 2024 10:52:18 +0300	[thread overview]
Message-ID: <ZZUSMoCAtoqsq5XV@lco.syogm.com> (raw)
In-Reply-To: <87v88c5m9j.fsf@tsdye.online>

* Thomas S. Dye <tsd@tsdye.online> [2024-01-02 08:39]:
> Aloha Ihor,
> 
> Ihor Radchenko <yantar92@posteo.net> writes:
> 
> > @@ -22,6 +22,10 @@ ** Summary
> >  It relies on a lightweight plain-text markup language used in  files
> >  with the =.org= extension.
> >   +Org files can be viewed using any text editor.  You can read and
> > +understand raw Org markup with a naked eye.  Although authoring Org
> > +files is best-supported inside Emacs.
> > +
> >  As an authoring tool, Org helps you write structured documents  and
> >  provides exporting facilities. Org files can also be used for  literate
> >  programming and reproducible research.  As a TODO lists  manager, Org
> > -- 
> > 2.42.0
> 
> How about this, assuming lightweight is equivalent to readable and easy to
> understand?
> 
> It relies on a readable and easy to understand plain-text markup language
> saved to files with the =.org= extension. Authoring Org files is best
> supported by Emacs, but you can view and change them with any text editor.
> As an authoring tool ...

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.

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.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/


  reply	other threads:[~2024-01-03 12:06 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 [this message]
2024-01-03 12:36     ` Bastien Guerry
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=ZZUSMoCAtoqsq5XV@lco.syogm.com \
    --to=bugs@gnu.support \
    --cc=bzg@gnu.org \
    --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).