From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: Re: application/emacs-lisp vs. application/x-emacs-lisp
Date: Wed, 20 Feb 2002 20:22:16 +0100 [thread overview]
Message-ID: <v9g03wc61j.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <2neljg47sb.fsf@zsh.cs.rochester.edu>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Wed, Feb 20 2002, ShengHuo ZHU wrote:
> Reiner Steib <4uce.02.r.steib@gmx.net> writes:
>> shouldn't the MIME types "application/emacs-lisp" and
>> "application/x-emacs-lisp" be handled in the same way by default?
>> Using the default settings with GNU Emacs 21.1.1 & Gnus from CVS,
>> emacs-lisp [1] is displayed inline, x-emacs-lisp not [2].
> Fixed.
not for me. You added "application/x-emacs-lisp" to `mm-inlined-types',
right? Apparently this is not sufficient. Know, after I changed
`mm-automatic-display' too, it works:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: changed mm-automatic-display in mm-decode.el --]
[-- Type: text/x-patch, Size: 799 bytes --]
Index: mm-decode.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mm-decode.el,v
retrieving revision 6.71
diff -u -r6.71 mm-decode.el
--- mm-decode.el 2002/02/20 13:04:54 6.71
+++ mm-decode.el 2002/02/20 19:09:45
@@ -254,7 +254,8 @@
'("text/plain" "text/enriched" "text/richtext" "text/html"
"text/x-vcard" "image/.*" "message/delivery-status" "multipart/.*"
"message/rfc822" "text/x-patch" "application/pgp-signature"
- "application/emacs-lisp" "application/x-pkcs7-signature"
+ "application/emacs-lisp" "application/x-emacs-lisp"
+ "application/x-pkcs7-signature"
"application/pkcs7-signature" "application/x-pkcs7-mime"
"application/pkcs7-mime")
"A list of MIME types to be displayed automatically."
[-- Attachment #3: Type: text/plain, Size: 321 bytes --]
Maybe the doc strings for `mm-inlined-types' and
`mm-automatic-display' aren't so clear. Shouldn't
`mm-automatic-display' be mentioned in the doc string of
`mm-inlined-types' (or vice versa)?
I also added an entry for "x-emacs-lisp" in `mailcap-mime-data' in
mailcap.el (Not necessary for this but maybe reasonable?):
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #4: changed mailcap-mime-data in mailcap.el --]
[-- Type: text/x-patch, Size: 570 bytes --]
Index: mailcap.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mailcap.el,v
retrieving revision 6.11
diff -u -r6.11 mailcap.el
--- mailcap.el 2002/02/20 00:15:32 6.11
+++ mailcap.el 2002/02/20 19:09:25
@@ -87,6 +87,9 @@
("emacs-lisp"
(viewer . mailcap-maybe-eval)
(type . "application/emacs-lisp"))
+ ("x-emacs-lisp"
+ (viewer . mailcap-maybe-eval)
+ (type . "application/x-emacs-lisp"))
("x-tar"
(viewer . mailcap-save-binary-file)
(non-viewer . t)
[-- Attachment #5: Type: text/plain, Size: 116 bytes --]
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2002-02-20 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 11:24 Reiner Steib
2002-02-20 13:11 ` ShengHuo ZHU
2002-02-20 19:22 ` Reiner Steib
2002-02-20 19:22 ` Reiner Steib [this message]
2002-02-20 20:19 ` ShengHuo ZHU
2002-02-20 20:19 ` ShengHuo ZHU
2002-02-20 13:11 ` ShengHuo ZHU
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 11:24 Reiner Steib
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=v9g03wc61j.fsf@marauder.physik.uni-ulm.de \
--to=4uce.02.r.steib@gmx.net \
--cc=reiner.steib@gmx.de \
/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.
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 NNTP newsgroup(s).