From: Adam Porter <adam@alphapapa.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, cnngimenez@disroot.org, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: SachaC-news
Date: Sun, 31 Dec 2023 15:36:40 -0600 [thread overview]
Message-ID: <3a6ed189-a56f-4249-9616-047724bc979a@alphapapa.net> (raw)
In-Reply-To: <83zfxq182m.fsf@gnu.org>
On 12/31/23 13:32, Eli Zaretskii wrote:
>> Date: Sun, 31 Dec 2023 12:13:24 -0600
>> Cc: cnngimenez@disroot.org, emacs-devel@gnu.org
>> From: Adam Porter <adam@alphapapa.net>
>>
>>> Org format is text with its own kind of markup -- it is not plain text.
>>
>> Many users would disagree.
>
> How can users disagree with something that is a plain fact?
A fact? Org's own web site, as I said, proclaims, "Your life in plain
text." It would seem there is at least room for interpretation.
>> If you look up promotional and educational
>> content about Org, you'll find that cited as one of its chief benefits:
>> that it's essentially plain text.
>
> "Essentially plain text" means it's not plain text.
What is "plain text"? Is the following block "plain text"?
To-do list:
- Walk dog
- Feed cat
- Reply to email
I would say so, as I've written many such lists in ".txt" files before I
discovered Org mode, yet it has Org syntax that would cause it to be
parsed as a paragraph followed by a bulleted list. If it is not "plain
text," then what would make it so? Shall we remove the hyphens?
To-do list:
Walk dog
Feed cat
Reply to email
Is that now "plain text"? Does that now qualify it for inclusion in an
Emacs package since it technically lacks Org syntax? (Or does it? Org
will parse that block as two paragraphs of Org-formatted text.) Is it
now easier to read outside of org-mode's font-locking?
> Do you deny that Org files have their own specialized markup? Because
> that's all that Richard said above. If you do agree that Org has its
> own markup, then where are you going with your objections and
> arguments?
He said that the package in question should have the output of one of
its commands changed to not output Org syntax. With Org being
"essentially" plain text, and intended to be readable as plain-text in
any software, without any special fontification, that raises the
question of what would be changed to qualify the command's output as
non-Org "plain text", and what the benefit would be to the user.
next prev parent reply other threads:[~2023-12-31 21:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 19:32 [ELPA] New package: SachaC-news Christian
2023-11-14 2:56 ` Richard Stallman
2023-11-15 23:56 ` Björn Bidar
2023-11-14 2:56 ` Richard Stallman
2023-11-18 20:26 ` Christian
2023-11-21 16:07 ` Sacha Chua
2023-11-25 22:40 ` Christian
2023-12-31 3:13 ` Richard Stallman
2023-12-31 18:13 ` Adam Porter
2023-12-31 19:32 ` Eli Zaretskii
2023-12-31 21:36 ` Adam Porter [this message]
2023-12-31 22:33 ` Christopher Dimech
2023-12-31 22:57 ` Emanuel Berg
2024-01-01 12:01 ` Eli Zaretskii
2024-01-02 3:19 ` Richard Stallman
2024-01-02 5:08 ` Emanuel Berg
2024-01-04 4:01 ` Richard Stallman
2024-01-02 18:05 ` Christian
2024-01-02 0:04 ` Stefan Kangas
2024-01-05 4:23 ` Richard Stallman
2024-01-02 17:40 ` Christian Gimenez
2023-11-17 7:28 ` Philip Kaludercic
2023-11-18 20:30 ` Christian
2023-11-18 21:10 ` Philip Kaludercic
2023-11-25 22:07 ` Christian
2023-11-25 22:50 ` Philip Kaludercic
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a6ed189-a56f-4249-9616-047724bc979a@alphapapa.net \
--to=adam@alphapapa.net \
--cc=cnngimenez@disroot.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.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).