Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Not prompting user in gnus-mime-delete-part and
Date: Mon, 29 Aug 2005 16:53:13 +0200	[thread overview]
Message-ID: <v9fysszteu.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mzmr1mw5t.fsf@jpl.org>

On Mon, Aug 29 2005, Katsumi Yamaoka wrote:

>>>>>> In <v93bou5ir0.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
>
>> On Sun, Aug 28 2005, Katsumi Yamaoka wrote:
>
>>> That message is an excuse to the function not being perfect, and
>>> there's not much likelihood that it will be completed.
>>> It will simply not work or really break articles if they have
>>> complex MIME structure, e.g., the case that a part is in a
>>> forwarded forwarded message.
>
>> Does the `mm-complicated-handles'-check cover all those cases?
>
> Yes, maybe.  (Although my worry is that it may also return `t'
> even for some MIME structure which won't cause a problem, it
> might be a needless fear since most of MIME composers cannot
> make such a complex structure.

Would it make sense to allow deleting/stripping despite of
"complicated handles" after an additional prompt instead of "giving
up"?

>> We could put a warning into the doc strings and the manual.
>
> I agree.

Would you like to add the warnings?

>> How about using the `gnus-expert-user' approach for
>> `gnus-mime-delete-part' and getting rid of the prompt completely for
>> `gnus-mime-save-part-and-strip'?
>
> I agree to do so, 

I've installed it.

> assuming those who set `gnus-expert-user' know what they do.

,----[ (info "(gnus)Splitting Mail") ]
| Gnus gives you all the opportunity you could possibly want for
| shooting yourself in the foot.
`----

:-)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2005-08-29 14:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 12:23 Not prompting user in gnus-mime-delete-part and gnus-mime-save-part-and-strip Reiner Steib
2005-08-27 20:57 ` Not prompting user in gnus-mime-delete-part and Dan Christensen
2005-08-28  0:32   ` Katsumi Yamaoka
2005-08-28 12:49     ` Reiner Steib
2005-08-29  0:19       ` Katsumi Yamaoka
2005-08-29 14:53         ` Reiner Steib [this message]
2005-08-30  1:36           ` Katsumi Yamaoka
2005-08-30  2:25         ` Dan Christensen
2005-08-30  6:07           ` Katsumi Yamaoka
2005-08-28 12:40   ` Imroving deleting/stripping MIME parts (was: Not prompting user in gnus-mime-delete-part and) Reiner Steib
2005-08-29 14:57     ` Imroving deleting/stripping MIME parts Reiner Steib
2005-08-30  2:22       ` Dan Christensen
2005-08-30 13:04         ` Reiner Steib
2005-08-30 15:25           ` Dan Christensen
2005-08-30 16:44             ` Reiner Steib
2005-08-31  4:18               ` Katsumi Yamaoka
2005-08-31 10:26                 ` Reiner Steib
2005-08-31 11:11                   ` Katsumi Yamaoka
2005-09-01  5:29                     ` Katsumi Yamaoka
2005-09-01 18:41                       ` Reiner Steib
2005-09-02  7:07                         ` Katsumi Yamaoka
2005-09-02 16:17                           ` Reiner Steib
2005-09-05  5:39                             ` Katsumi Yamaoka
2005-09-05 13:15                               ` Reiner Steib

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=v9fysszteu.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.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).