Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Imroving deleting/stripping MIME parts
Date: Fri, 02 Sep 2005 16:07:32 +0900	[thread overview]
Message-ID: <b4m64tkaqx7.fsf@jpl.org> (raw)
In-Reply-To: <v9ll2gy6jw.fsf@marauder.physik.uni-ulm.de>

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

>>>>> In <v9ll2gy6jw.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:

> I worked for my test cases.  Please install.

Done.

> There is still the problem (probably with `gnus-article-goto-part';
> unrelated to your code), that using `d' repeatedly in a message with
> several attachments sometimes fails to advance to the next part (with
> `gnus-auto-select-part' set to 1).

If you're talking about the case where there are not only
buttonized parts but also unbuttonized parts in the article,
does the following patch solve it?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 622 bytes --]

--- gnus-art.el~	2005-09-01 22:14:44 +0000
+++ gnus-art.el	2005-09-02 07:06:35 +0000
@@ -4122,7 +4122,16 @@
 			    n parts)
 	      parts)))
     (gnus-message 9 "Jumping to part %s." n)
-    (gnus-article-goto-part n)))
+    (cond ((>= gnus-auto-select-part 1)
+	   (while (and (<= n parts)
+		       (not (gnus-article-goto-part n)))
+	     (setq n (1+ n))))
+	  ((< gnus-auto-select-part 0)
+	   (while (and (>= n 1)
+		       (not (gnus-article-goto-part n)))
+	     (setq n (1- n))))
+	  (t
+	   (gnus-article-goto-part n)))))
 
 (eval-when-compile
   (defsubst gnus-article-edit-part (handles &optional current-id)

  reply	other threads:[~2005-09-02  7:07 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
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 [this message]
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=b4m64tkaqx7.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).