From: Colin Rafferty <craffert@ms.com>
Subject: [patch] choose best looking alternative
Date: 22 Apr 1999 11:30:37 -0400 [thread overview]
Message-ID: <vgv7lr4llk2.fsf@ms.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
According to some RFC, a multipart/alternative is supposed to be in
order of human readable, and reverse order of prettiness when
displayed.
I just upgraded from 0.80 to 0.83, and the implied precedence order
was is reversed.
[-- Attachment #2.1: Type: text/plain, Size: 84 bytes --]
An example is this line. It *should* be in text/enriched, but it's in
text/plain.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.2: Type: text/enriched, Size: 95 bytes --]
An example is this line. It <bold>should</bold> be in text/enriched,
but it's in text/plain.
[-- Attachment #3: Type: text/plain, Size: 714 bytes --]
Anyway, here is the patch:
1999-04-22 Colin Rafferty <colin@xemacs.org>
* mm-decode.el (mm-preferred-alternative-precedence): Later
handles are nicer than earlier handles.
--- mm-decode.el~ Sun Apr 18 08:44:10 1999
+++ mm-decode.el Thu Apr 22 11:10:19 1999
@@ -586,7 +586,7 @@
(defun mm-preferred-alternative-precedence (handles)
"Return the precedence based on HANDLES and mm-discouraged-alternatives."
- (let ((seq (mapcar (lambda (h) (car (mm-handle-type h))) handles)))
+ (let ((seq (mapcar (lambda (h) (car (mm-handle-type h))) (reverse handles))))
(dolist (disc (reverse mm-discouraged-alternatives))
(dolist (elem (copy-sequence seq))
(when (string-match disc elem)
--
Colin
next reply other threads:[~1999-04-22 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-22 15:30 Colin Rafferty [this message]
1999-04-22 17:59 ` François Pinard
1999-04-22 17:10 ` paul stevenson
1999-04-22 18:26 ` Alexandre Oliva
1999-04-22 18:27 ` Colin Rafferty
1999-04-22 18:29 ` Colin Rafferty
1999-04-22 21:45 ` François Pinard
1999-04-22 21:55 ` Colin Rafferty
1999-04-22 18:36 ` Raja R Harinath
1999-04-22 21:49 ` François Pinard
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=vgv7lr4llk2.fsf@ms.com \
--to=craffert@ms.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.
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).