Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Bug in deleting attachments
Date: Tue, 02 Mar 2004 19:50:07 +0100	[thread overview]
Message-ID: <m3ishnks8m.fsf@hamster.pflaesterer.de> (raw)

Hi,
today I tried to delete an attachment and always got the annoying error
message: `This function is not implemented' (btw I find it misleading
because the function is indeed implemented).

I searched for the reason and found in `gnus-mime-delete-part' the
following code:

      (if (mm-multiple-handles gnus-article-mime-handles)
	  (error "This function is not implemented"))

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)))))


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 was in a nnml group (which supports article editing) and the
application of mm-multiple-handles on that value gives t which returns
that error message (which is that just wrong here).

I changed the definition of `mm-multiple-handles' so that nil was
returned and the function `gnus-mime-delete-part' ran without problem.

I'm not sure at the moment what the exact reason of the bug is (I don't
know what `mm-multiple-handles' is exactly testing).  Can anyone shed
some light on that?


   KP

-- 
      And has thou slain the Jabberwock?
          Come to my arms, my beamish boy!
      O frabjous day!  Callooh!  Callay!'
          He chortled in his joy.   "Lewis Carroll" "Jabberwocky"



             reply	other threads:[~2004-03-02 18:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 18:50 Karl Pflästerer [this message]
2004-03-02 20:11 ` Reiner Steib
2004-03-02 22:42   ` Karl Pflästerer
2004-03-02 23:23   ` Katsumi Yamaoka
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=m3ishnks8m.fsf@hamster.pflaesterer.de \
    --to=sigurd@12move.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).