From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Bug in deleting attachments
Date: Wed, 03 Mar 2004 08:23:36 +0900 [thread overview]
Message-ID: <b9yd67uj0jr.fsf@jpl.org> (raw)
In-Reply-To: <v9n06zggbe.fsf@marauder.physik.uni-ulm.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 2923 bytes --]
>>>>> In <m3ishnks8m.fsf@hamster.pflaesterer.de>
>>>>> sigurd@12move.de (Karl Pfl^[.A^[Ndsterer) wrote:
> I looked further and saw that definition of `mm-multiple-handles'
> (defun mm-multiple-handles (handles)
> (and (listp handles)
> (> (length handles) 1)
> (or (listp (car handles))
> (stringp (car handles)))))
I changed it to be used by the mm-w3m-cid-retrieve-1 function so
that it detects multiple handles in the strict sense of the name:
2004-01-15 Katsumi Yamaoka <yamaoka@jpl.org>
* mm-decoce.el (mm-multiple-handles): Recognize a string as a mime
handle, as well as a list.
;; Oops, there's a typo!
The function definition used to be:
(defun mm-multiple-handles (handles)
(and (listp (car handles))
(> (length handles) 1)))
> The value of `gnus-article-mime-handles' in that case was:
> ("multipart/mixed" (#<buffer " *mm*<2>"> ("text/html" (charset .
> "us-ascii")) 7bit (lambda nil (let (buffer-read-only) (delete-region
> #<marker at 190 in *Article nnml+private:mail.other2004-02* 0x11b46f3c>
> #<marker at 1206 in *Article nnml+private:mail.other2004-02*
0x11b46f54>))) nil nil nil nil) (#<buffer " *mm*<3>">
> ("application/x-zip-compressed" (name . "Raging Cajun.zip")) base64 nil
> ("inline" (filename . "Raging Cajun.zip")) nil nil nil)))
It is reasonable that the present mm-multiple-handles returns t
for that case, isn't it? :)
>>>>> In <v9n06zggbe.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> wrote:
> First, I have to admit that the code of `gnus-mime-delete-part' is
> more or less copied from `gnus-mime-save-part-and-strip' (see the
> FIXME). In `gnus-mime-save-part-and-strip' ShengHuo added this check
> deliberately:
> ,----[ <news:2n664zyl41.fsf@zsh.cs.rochester.edu> ]
>| From: ShengHuo ZHU <zsh@cs.rochester.edu>
>| Subject: Re: remove attachments
>| Newsgroups: gnu.emacs.gnus
>| Date: Thu, 14 Feb 2002 13:27:42 -0500
>| Message-ID: <2n664zyl41.fsf@zsh.cs.rochester.edu>
>|
>| Reiner Steib <4uce.02.r.steib@gmx.net> writes:
>| [...]
>|> Is it possible to strip a part that's inside a forwarded messsage
>|> (Content-Type: message/rfc822)? I'd like to strip the
>|> `application/msword' part from the following message (I get
>|> `gnus-mime-save-part-and-strip: This function is not implemented'):
>|
>| I disabled this feature on messages with complicated MIME structures
>| because of some difficulties, such as locating the part, PGP or S/MIME
>| stuff, etc. Anyway, you can always edit the message manually if the
>| back end supports it.
> `----
> But maybe we can change the error into a query like "Deleting parts in
> complicated MIME structures might not work. Are you sure?"?
And we probably have to provide the new function for that
purpose like:
(defun mm-complicated-handles (handles)
(and (listp (car handles))
(> (length handles) 1)))
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-03-02 23:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 18:50 Karl Pflästerer
2004-03-02 20:11 ` Reiner Steib
2004-03-02 22:42 ` Karl Pflästerer
2004-03-02 23:23 ` Katsumi Yamaoka [this message]
2004-03-03 0:54 ` Karl Pflästerer
2004-03-07 10:23 ` Stephen Berman
2004-03-09 8:37 ` Katsumi Yamaoka
2004-03-10 10:04 ` Stephen Berman
2004-03-10 11:52 ` Katsumi Yamaoka
2004-03-10 12:52 ` Stephen Berman
2004-03-10 23:41 ` Katsumi Yamaoka
2004-03-11 11:30 ` Katsumi Yamaoka
2004-03-12 9:21 ` Stephen Berman
2004-03-12 11:19 ` Katsumi Yamaoka
2004-03-12 13:46 ` Stephen Berman
2004-03-13 11:55 ` Kai Grossjohann
2004-03-15 6:07 ` Katsumi Yamaoka
2004-03-19 11:36 ` Katsumi Yamaoka
2004-03-19 11:46 ` Katsumi Yamaoka
2004-03-19 11:53 ` Katsumi Yamaoka
2004-03-23 8:26 ` 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=b9yd67uj0jr.fsf@jpl.org \
--to=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).