Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Bug in deleting attachments
Date: Tue, 02 Mar 2004 23:42:31 +0100	[thread overview]
Message-ID: <m3ishmkhd4.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <v9n06zggbe.fsf@marauder.physik.uni-ulm.de>

On  2 Mar 2004, 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:

Maybe if someone has the time and the knowledge he could write one
function which incorporates the common code (maybe even
`gnus-mime-save-part-and-strip' could just call `gnus-mime-delete-part'
and do some additional work).

> ,----[ <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?"?

That would definitley be better; at the moment I feeled as Gnus wanted
to stultify me saying a function was not implemented which indeed
existed.

Perhaps ShengHuo could explain where the problems are and we could find
a solution.  Manually editing isn't a real alternative IMO (you
shouldn't have to be a hacker to be able to use Gnus).

 
   KP

-- 
And as in uffish thought he stood,
The Jabberwock, with eyes of flame,
Came whiffling through the tulgey wood,
And burbled as it came!                "Lewis Carroll" "Jabberwocky"



  reply	other threads:[~2004-03-02 22:42 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 [this message]
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=m3ishmkhd4.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).