From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Not prompting user in gnus-mime-delete-part and
Date: Sun, 28 Aug 2005 14:49:23 +0200 [thread overview]
Message-ID: <v93bou5ir0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4moe7iq4t6.fsf@jpl.org>
On Sun, Aug 28 2005, Katsumi Yamaoka wrote:
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>>> I'd like to have an option in Gnus to get rid of the prompt "Deleting
>>> parts may malfunction or destroy the article; continue?" when deleting
>>> or stripping attachments.
>
>>>>>> In <87r7cfxfma.fsf@uwo.ca>
>>>>>> Dan Christensen <jdc@uwo.ca> wrote:
>
>> I'd suggest just getting rid of that question (which is how this
>> function used to behave).
>
> 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?
> But I also feel that message is noisy, so I agree to get rid of it.
> I think another way is required for saying it is imperfect, though.
We could put a warning into the doc strings and the manual.
>> The user still needs to specify the filename, and that prompt could
>> be changed to read
>>
>> Delete MIME part and save to:
>>
>> The user can hit C-g at this point to abort.
But not for `gnus-mime-delete-part'. Accidentally pressing `d' on a
MIME part instead in the Summary buffer or the rest of the Article
buffer gives quite different results:
`gnus-summary-mark-as-read-forward' vs. `gnus-mime-delete-part'.
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'?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-08-28 12:49 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 [this message]
2005-08-29 0:19 ` Katsumi Yamaoka
2005-08-29 14:53 ` Reiner Steib
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=v93bou5ir0.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).