Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: Various nnimap problems
Date: Fri, 24 Sep 2010 11:06:58 -0400	[thread overview]
Message-ID: <87sk0z41v1.fsf@maru.md5i.com> (raw)
In-Reply-To: <m3tylhirt4.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 22 Sep 2010 19:58:15 +0200")

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

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Michael Welsh Duggan <mwd@cert.org> writes:
>
>> *) On Exchange, I am seeing the 'junk split from nnmail-split-fancy not
>>    actually deleting the message.
>
> This is now implemented.

Thank you.  This seems to work for the most part.  However, looking at
the code, it looks like if the only items in the inbox are marked as
'junk, they are not deleted.  This looks like a minor paren bug.  One
two few parens at then end of the (when sequences) clause in
nnimap-split-incoming-mail, and one too many at the end.


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

diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 2d4f0de..42fe4d4 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -1154,8 +1154,8 @@ not done by default on servers that doesn't support that command.")
 	      ;; And then mark the successful copy actions as deleted,
 	      ;; and possibly expunge them.
 	      (nnimap-mark-and-expunge-incoming
-	       (nnimap-parse-copied-articles sequences))
-	      (nnimap-mark-and-expunge-incoming junk-articles))))))))
+	       (nnimap-parse-copied-articles sequences)))
+            (nnimap-mark-and-expunge-incoming junk-articles)))))))
 
 (defun nnimap-mark-and-expunge-incoming (range)
   (when range

[-- Attachment #3: Type: text/plain, Size: 42 bytes --]


-- 
Michael Welsh Duggan
(md5i@md5i.com)

  reply	other threads:[~2010-09-24 15:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 15:40 Michael Welsh Duggan
2010-09-22 15:57 ` Michael Welsh Duggan
2010-09-22 16:39 ` Julien Danjou
2010-09-22 17:09   ` Julien Danjou
2010-09-22 17:16     ` Lars Magne Ingebrigtsen
2010-09-22 17:23       ` Lars Magne Ingebrigtsen
2010-09-22 17:13 ` Lars Magne Ingebrigtsen
2010-09-22 17:46   ` Michael Welsh Duggan
2010-09-22 18:45     ` Lars Magne Ingebrigtsen
2010-09-22 18:31   ` Michael Welsh Duggan
2010-09-22 18:36     ` Lars Magne Ingebrigtsen
2010-09-22 21:06     ` Michael Welsh Duggan
2010-09-22 21:33       ` Lars Magne Ingebrigtsen
2010-09-22 22:49         ` Michael Welsh Duggan
2010-09-22 22:53         ` Michael Welsh Duggan
2010-09-26 18:25           ` Michael Welsh Duggan
2010-09-26 18:57             ` Lars Magne Ingebrigtsen
2010-09-22 17:58 ` Lars Magne Ingebrigtsen
2010-09-24 15:06   ` Michael Welsh Duggan [this message]
2010-09-24 16:04     ` Lars Magne Ingebrigtsen

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=87sk0z41v1.fsf@maru.md5i.com \
    --to=md5i@md5i.com \
    --cc=ding@gnus.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).