From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: mml-generate-default-type
Date: Wed, 27 Jul 2005 15:14:17 +0200 [thread overview]
Message-ID: <v964uwxufq.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
`M-x grep RET mml-generate-default-type SPC *.el RET' (in the v5-10
branch) gives:
,----
| grep -nH -e mml-generate-default-type *.el
| mml.el:126:(defvar mml-generate-default-type "text/plain")
| mml.el:440: (mml-generate-default-type "text/plain"))
| mml.el:537: (mml-generate-default-type (if (equal type "digest")
| mml.el:633: (not (equal type mml-generate-default-type))
`----
(1) Is there a good reason for the let-binding in line 440?
(let ((mml-boundary (mml-compute-boundary cont))
(mml-generate-default-type "text/plain"))
(mml-to-mime))
(2) The code...
(when (or charset
parameters
flowed
(not (equal type mml-generate-default-type))
mml-insert-mime-headers-always)
[...]
(insert "Content-Type: " type)
... suggests that `mml-generate-default-type' is the default
Content-Type that doesn't need to be declared according to the
relevant RFC(s). In this case, `mml-generate-default-type' should
probably be a constant, I think. And it should get a doc string.
Bye, Reiner.
[ Cc-ing Katsumi, who pointed me to `mml-generate-default-type' while
discussing a problem with `mml-attach-file'. Hopefully the ding
list will soon be up again. ]
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next reply other threads:[~2005-07-27 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 13:14 Reiner Steib [this message]
2005-07-28 5:39 ` mml-generate-default-type Katsumi Yamaoka
2005-07-28 13:14 ` mml-generate-default-type Reiner Steib
2005-07-28 22:23 ` mml-generate-default-type Katsumi Yamaoka
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=v964uwxufq.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=yamaoka@jpl.org \
/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).