From: Max Nikulin <manikulin@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>, 68687@debbugs.gnu.org
Cc: emacs-orgmode@gnu.org
Subject: bug#68687: [PATCH v2] Use text/org media type
Date: Fri, 2 Feb 2024 23:28:17 +0700 [thread overview]
Message-ID: <1882c330-a58a-4c0a-adf1-6801e09f3b81@gmail.com> (raw)
In-Reply-To: <CADwFkmknBZj0Y4H=Nwqa4sH0uQAsP70kWtMU33ZgfRiuWkX9_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
I am sending an updated version of the patch, earlier I missed one
occurrence of text/org.
I am leaving it up to you the decision concerning mailcap.el.
On 02/02/2024 14:09, Stefan Kangas wrote:
> So why not:
>
> 1. Add support for _receiving_ "text/org" in Emacs 30
> 2. Wait with _sending_ "text/org" until it is formally accepted by IANA
I do not mind. I just do not see real reasons to do so taking into
account applicaion/vnd.lotus-organizer in Emacs and text/org in XDG.
>> Create ~/.mime.types. Debian's variant suggests it in the
>> /etc/mime.types header.
>
> Is that documented somewhere in our documentation?
Likely it is not. It is documented in man pages for various tools. In
Emacs-27 mailcap.el was severely broken, so I do not expect detailed
documentation.
> Yes, that would be best. While waiting for that to happen, why not do
> what I proposed (override it unconditionally in Emacs)? It should be
> more useful for Emacs users, if nothing else.
It has happened so that I has spent some time reading Python bug tracker
concerning their mimetypes module. I suggest against doing it
unconditionally. Give users controls what sources should be used and
what priority each source should have (application internal mapping,
system-wide configuration files, user configuration files, Windows
registry, XDG files as possible future improvement). Inconsistencies are
not uncommon, updates of the IANA registry are applied with different pace.
> Taking a step back, how sure are we that IANA will accept this? Do they
> typically accept taking over a previous designation?
An alternative is to negotiate with maintainers of mime.types in RedHat
and Debian. My first impression is that in the case of Debian it may
take enough time before any reaction. I am unsure as well that IANA will
agree to change media type for .org without approval from IBM.
[-- Attachment #2: v2-0001-Use-text-org-media-type.patch --]
[-- Type: text/x-patch, Size: 2833 bytes --]
From 9f0950075bbfbfc1ff1080ee410c66e1953197d7 Mon Sep 17 00:00:00 2001
From: Max Nikulin <manikulin@gmail.com>
Date: Wed, 24 Jan 2024 21:16:28 +0700
Subject: [PATCH v2] Use text/org media type
Avoid "x-" prefix deprecated by rfc6648 for Org mode media type.
* lisp/net/mailcap.el (mailcap-mime-extensions):
* lisp/gnus/mm-uu.el (mm-uu-org-src-code-block-extract): Replace
text/x-org by text/org.
* lisp/gnus/mm-decode.el (mm-inline-media-tests, mm-automatic-display):
Allow text/org in addition to text/x-org.
Make media type defined for Org mode consistent with
<https://gitlab.freedesktop.org/xdg/shared-mime-info>
See emacs-orgmode: Org mode MIME type. Sun, 21 Jan 2024 20:56:15 +0700.
https://list.orgmode.org/6d94fff4-4d30-4121-bfd1-f267cb5b637c@gmail.com
---
lisp/gnus/mm-decode.el | 2 ++
lisp/gnus/mm-uu.el | 2 +-
lisp/net/mailcap.el | 3 ++-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/lisp/gnus/mm-decode.el b/lisp/gnus/mm-decode.el
index f91755e967b..8086c97fe55 100644
--- a/lisp/gnus/mm-decode.el
+++ b/lisp/gnus/mm-decode.el
@@ -246,6 +246,7 @@ (defcustom mm-inline-media-tests
("text/x-sh" mm-display-shell-script-inline identity)
("application/javascript" mm-display-javascript-inline identity)
("text/dns" mm-display-dns-inline identity)
+ ("text/org" mm-display-org-inline identity)
("text/x-org" mm-display-org-inline identity)
("text/html"
mm-inline-text-html
@@ -336,6 +337,7 @@ (defcustom mm-automatic-display
"application/pkcs7-mime"
;; Mutt still uses this even though it has already been withdrawn.
"application/pgp\\'"
+ "text/org"
"text/x-org")
"A list of MIME types to be displayed automatically."
:type '(repeat regexp)
diff --git a/lisp/gnus/mm-uu.el b/lisp/gnus/mm-uu.el
index 3c7e3cbdf1a..b10da0c143a 100644
--- a/lisp/gnus/mm-uu.el
+++ b/lisp/gnus/mm-uu.el
@@ -394,7 +394,7 @@ (defun mm-uu-emacs-sources-extract ()
(defun mm-uu-org-src-code-block-extract ()
(mm-make-handle (mm-uu-copy-to-buffer start-point end-point)
- '("text/x-org" (charset . gnus-decoded))))
+ '("text/org" (charset . gnus-decoded))))
(defvar gnus-newsgroup-name)
diff --git a/lisp/net/mailcap.el b/lisp/net/mailcap.el
index 5ff75deb4e6..900099433c4 100644
--- a/lisp/net/mailcap.el
+++ b/lisp/net/mailcap.el
@@ -989,7 +989,8 @@ (defvar mailcap-mime-extensions
(".jpe" . "image/jpeg")
(".jpeg" . "image/jpeg")
(".webp" . "image/webp")
- (".org" . "text/x-org"))
+ ;; May be overridden by application/vnd.lotus-organizer in /etc/mime.types.
+ (".org" . "text/org"))
"An alist of file extensions and corresponding MIME content-types.
This exists for you to customize the information in Lisp. It is
merged with values from mailcap files by `mailcap-parse-mimetypes'.")
--
2.39.2
prev parent reply other threads:[~2024-02-02 16:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6d94fff4-4d30-4121-bfd1-f267cb5b637c@gmail.com>
[not found] ` <8734uqpvgn.fsf@tec.tecosaur.net>
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:23 ` Eli Zaretskii
2024-01-26 10:39 ` Max Nikulin
2024-01-26 12:22 ` Eli Zaretskii
2024-01-31 16:30 ` Max Nikulin
[not found] ` <87h6j1f08d.fsf@localhost>
2024-01-26 7:40 ` Eli Zaretskii
2024-01-26 10:52 ` Max Nikulin
[not found] ` <86h6j0bl0m.fsf@gnu.org>
2024-01-26 14:00 ` Ihor Radchenko
2024-01-30 19:39 ` Stefan Kangas
[not found] ` <CADwFkm=9EwTZwa3F4wGJVPAVgcW4KXS1kPzXLPg1msYDjJL2cw@mail.gmail.com>
2024-01-30 20:34 ` Ihor Radchenko
2024-01-27 3:38 ` Richard Stallman
[not found] ` <E1rTZWZ-0008Ca-EM@fencepost.gnu.org>
2024-01-28 16:35 ` Max Nikulin
2024-01-28 16:47 ` Eli Zaretskii
[not found] ` <8634uh5rrq.fsf@gnu.org>
2024-01-30 3:56 ` Richard Stallman
[not found] ` <E1rUfF4-00069N-Gu@fencepost.gnu.org>
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:51 ` Ihor Radchenko
[not found] ` <87mssmvhdw.fsf@localhost>
2024-02-02 3:38 ` Richard Stallman
2024-02-02 4:58 ` bug#68687: Org mode code evaluation Max Nikulin
2024-01-31 16:18 ` bug#68687: [PATCH] Use text/org media type Max Nikulin
[not found] ` <3c8e8b77-77d1-4522-85d5-5cce2cc020ca@gmail.com>
2024-01-31 16:32 ` Ihor Radchenko
2024-02-02 3:40 ` Richard Stallman
[not found] ` <E1rVkPO-0008LA-RN@fencepost.gnu.org>
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
[not found] ` <CADwFkmknBZj0Y4H=Nwqa4sH0uQAsP70kWtMU33ZgfRiuWkX9_w@mail.gmail.com>
2024-02-02 16:28 ` Max Nikulin [this message]
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=1882c330-a58a-4c0a-adf1-6801e09f3b81@gmail.com \
--to=manikulin@gmail.com \
--cc=68687@debbugs.gnu.org \
--cc=emacs-orgmode@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 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).