From: "Thomas S. Dye" <tsd@tsdye.online>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] doc/org-manual.org (Summary): Clarify the Org markup is human-readable
Date: Mon, 01 Jan 2024 19:24:06 -1000 [thread overview]
Message-ID: <87v88c5m9j.fsf@tsdye.online> (raw)
In-Reply-To: <87il4e75u8.fsf@localhost>
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 ...
All the best,
Tom
--
Thomas S. Dye https://tsdye.online/tsdye
next prev parent reply other threads:[~2024-01-02 5: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 [this message]
2024-01-03 7:52 ` Jean Louis
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=87v88c5m9j.fsf@tsdye.online \
--to=tsd@tsdye.online \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--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).