From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: manikulin@gmail.com, 68687@debbugs.gnu.org,
emacs-orgmode@gnu.org, stefankangas@gmail.com
Subject: Re: bug#68687: [PATCH] Use text/org media type
Date: Mon, 29 Jan 2024 22:56:58 -0500 [thread overview]
Message-ID: <E1rUfF4-00069N-Gu@fencepost.gnu.org> (raw)
In-Reply-To: <8634uh5rrq.fsf@gnu.org> (message from Eli Zaretskii on Sun, 28 Jan 2024 18:47:37 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I think Richard lacks the broader context: that text/org is supposed
> to appear in the Content-Type header in email messages, and the MUA is
> supposed to display this content in received email messages according
> to user expectations, which generally follow how Org buffers display
> text.
Thanks/ I had a feeling that it was something along roughtly those
lines, but I was not sure. Now I know.
I am concerned that the actions described above would tend to embed
Org format and Org mode more deeply into Emacs usage.
Suppose A and B are Org users. If A knows this, and mails B a message
which contains text labaled as text/org, that won't make anyone
unhappy. No one would have a reason to complain.
But what if C mails a message to D with text labeled as text/org and D
is not an Org user? Will that cause Emacs to load Org? It should
not.
What will Gnus do when the user readss a message with text labaled as
text/org? What will Rmail do? What will MH-E do?
These are crucial questions because the answers would determine
whether this feature pressures people to use Org mode or not. We need
concrete answers because only that would enable us to see cleary now
whether the feature would do that if in use.
Max Nikulin <manikulin@gmail.com> wrote:
Received or fetched Org
> files must be treated with some precautions, but it is another story.
I was not aware of this issue. Let's look at it concretely now so we
can determine what its implications are. Have people already written
a list of these precautions? If so, I'd like to see it.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-01-30 3:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 13:56 Org mode MIME type Max Nikulin
2024-01-21 15:11 ` Timothy
2024-01-22 16:21 ` Max Nikulin
2024-01-24 14:43 ` bug#68687: [PATCH] Use text/org media type Max Nikulin
2024-01-25 23:10 ` Stefan Kangas
2024-01-25 23:43 ` Ihor Radchenko
2024-01-26 7:40 ` Eli Zaretskii
2024-01-26 14:00 ` Ihor Radchenko
2024-01-30 19:39 ` Stefan Kangas
2024-01-30 20:34 ` Ihor Radchenko
2024-01-26 7:23 ` Eli Zaretskii
2024-01-31 16:30 ` Max Nikulin
2024-01-27 3:38 ` Richard Stallman
2024-01-28 16:35 ` Max Nikulin
2024-01-28 16:47 ` Eli Zaretskii
2024-01-30 3:56 ` Richard Stallman [this message]
2024-01-30 12:13 ` Ihor Radchenko
2024-01-30 17:12 ` Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type) Mike Kupfer
2024-01-30 17:51 ` Ihor Radchenko
2024-02-02 3:38 ` bug#68687: " Richard Stallman
2024-02-02 4:58 ` bug#68687: Org mode code evaluation Max Nikulin
2024-02-02 16:10 ` bug#68687: Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type) Ihor Radchenko
2024-01-31 16:18 ` bug#68687: [PATCH] Use text/org media type Max Nikulin
2024-01-31 16:32 ` Ihor Radchenko
2024-02-02 3:40 ` Richard Stallman
2024-02-02 7:15 ` Eli Zaretskii
2024-01-30 12:52 ` Eli Zaretskii
2024-01-31 20:00 ` Stefan Kangas
2024-02-01 10:40 ` Max Nikulin
2024-02-02 7:09 ` Stefan Kangas
2024-02-02 16:28 ` bug#68687: [PATCH v2] " Max Nikulin
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=E1rUfF4-00069N-Gu@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=68687@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=stefankangas@gmail.com \
/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).