From: Eli Zaretskii <eliz@gnu.org>
To: Max Nikulin <manikulin@gmail.com>
Cc: rms@gnu.org, stefankangas@gmail.com, 68687@debbugs.gnu.org,
emacs-orgmode@gnu.org
Subject: Re: bug#68687: [PATCH] Use text/org media type
Date: Sun, 28 Jan 2024 18:47:37 +0200 [thread overview]
Message-ID: <8634uh5rrq.fsf@gnu.org> (raw)
In-Reply-To: <74b83cf9-cd7e-429a-bd9d-0af964e1ddc5@gmail.com> (message from Max Nikulin on Sun, 28 Jan 2024 23:35:09 +0700)
> Cc: 68687@debbugs.gnu.org, emacs-orgmode@gnu.org
> Date: Sun, 28 Jan 2024 23:35:09 +0700
> From: Max Nikulin <manikulin@gmail.com>
>
> On 27/01/2024 10:38, Richard Stallman wrote:
> >
> > What is the purpose for which text/org would be used?
> > In what situations would we want to send files in Org format
> > and why would it be useful to formally label them?
>
> I am rather confused by these questions. Media types appears in the
> Content-Type header. Applications decide how to treat content basing on
> media type description. E.g. Thunderbird may be configured to display
> text attachments inline, but if the same attachment uses
> application/vnd.lotus-organizer then an external application must be
> invoked to see its text.
>
> De-facto Org files are used in various projects. Received or fetched Org
> files must be treated with some precautions, but it is another story.
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.
next prev parent reply other threads:[~2024-01-28 16:49 UTC|newest]
Thread overview: 59+ 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:10 ` Stefan Kangas
2024-01-25 23:43 ` Ihor Radchenko
2024-01-26 7:40 ` Eli Zaretskii
2024-01-26 7:40 ` Eli Zaretskii
2024-01-26 14:00 ` Ihor Radchenko
2024-01-26 14:00 ` Ihor Radchenko
2024-01-26 10:52 ` Max Nikulin
2024-01-30 19:39 ` Stefan Kangas
2024-01-30 19:39 ` Stefan Kangas
2024-01-30 20:34 ` Ihor Radchenko
2024-01-30 20:34 ` Ihor Radchenko
2024-01-25 23:43 ` Ihor Radchenko
2024-01-26 7:23 ` Eli Zaretskii
2024-01-26 7:23 ` Eli Zaretskii
2024-01-26 10:39 ` Max Nikulin
2024-01-26 12:22 ` Eli Zaretskii
2024-01-31 16:30 ` Max Nikulin
2024-01-31 16:30 ` Max Nikulin
2024-01-27 3:38 ` Richard Stallman
2024-01-27 3:38 ` Richard Stallman
2024-01-28 16:35 ` Max Nikulin
2024-01-28 16:35 ` Max Nikulin
2024-01-28 16:47 ` Eli Zaretskii [this message]
2024-01-30 3:56 ` Richard Stallman
2024-01-30 12:13 ` Ihor Radchenko
2024-01-30 12:13 ` Ihor Radchenko
2024-01-30 17:12 ` bug#68687: Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type) Mike Kupfer
2024-01-30 17:12 ` Mike Kupfer
2024-01-30 17:51 ` bug#68687: " Ihor Radchenko
2024-01-30 17:51 ` Ihor Radchenko
2024-02-02 3:38 ` bug#68687: " Richard Stallman
2024-02-02 3:38 ` Richard Stallman
2024-02-02 4:58 ` bug#68687: Org mode code evaluation Max Nikulin
2024-02-02 4:58 ` 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:18 ` Max Nikulin
2024-01-31 16:32 ` Ihor Radchenko
2024-01-31 16:32 ` Ihor Radchenko
2024-02-02 3:40 ` Richard Stallman
2024-02-02 3:40 ` Richard Stallman
2024-02-02 7:15 ` Eli Zaretskii
2024-02-02 7:15 ` Eli Zaretskii
2024-01-30 12:52 ` Eli Zaretskii
2024-01-30 12:52 ` Eli Zaretskii
2024-01-30 3:56 ` Richard Stallman
2024-01-28 16:47 ` Eli Zaretskii
2024-01-31 20:00 ` Stefan Kangas
2024-01-31 20:00 ` Stefan Kangas
2024-02-01 10:40 ` Max Nikulin
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
2024-02-02 7:09 ` bug#68687: [PATCH] " Stefan Kangas
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=8634uh5rrq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68687@debbugs.gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=rms@gnu.org \
--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 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.