Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Brierley <brierley@pobox.com>
Subject: [PATCH] nnimap: Checking mailbox %s vs. Updating info for %s
Date: 20 Apr 2000 16:20:42 -0400	[thread overview]
Message-ID: <wkln28bk2t.fsf@pobox.com> (raw)

A couple of months ago I sent in a bug report detailing how moving
or copying a message from an nnimap group on one IMAP server to an
nnimap group on another IMAP server causes a bogus server entry in
the *Server* buffer with the result that subsequent invocations of
gnus-group-get-new-news cause the dreaded "Updating info for %s"
vs. the much faster "Checking mailbox %s".

Simon sent out a patch which resolved this problem, and which I've
been using successfuly since.  I just installed Gnus 5.8.4 and it
looks like Simon's patch didn't make it into the release.  I've
applied his patch to 5.8.4 and it still fixes the bug without
apparent problems.

So, I'm including Simon's patch here in the hopes that it can be
added to CVS.  Thanks.

,-----[ Patch to gnus-sum.el
| 2000-03-01  Simon Josefsson  <jas@pdc.kth.se>
| 
|         * gnus-sum.el (gnus-read-move-group-name): 
|         (gnus-summary-move-article): Use `gnus-group-method' to find out
|         what method the manually entered group belong to.
|         `gnus-group-name-to-method' doesn't return any method parameters
|         and `gnus-find-method-for-group' uses `gnus-group-name-to-method'
|         for new groups so they wouldn't work.
| 
| Index: lisp/gnus-sum.el
| ===================================================================
| RCS file: /usr/local/cvsroot/gnus/lisp/gnus-sum.el,v
| retrieving revision 5.97
| diff -w -u -r5.97 gnus-sum.el
| --- lisp/gnus-sum.el	2000/02/03 16:28:49	5.97
| +++ lisp/gnus-sum.el	2000/03/01 19:45:52
| @@ -7322,7 +7322,7 @@
|              articles prefix))
|        (set (intern (format "gnus-current-%s-group" action)) to-newsgroup))
|      (setq to-method (or select-method
| -			(gnus-group-name-to-method to-newsgroup)))
| +			(gnus-group-method to-newsgroup)))
|      ;; Check the method we are to move this article to...
|      (unless (gnus-check-backend-function
|              'request-accept-article (car to-method))
| @@ -9027,14 +9027,15 @@
|        (unless to-newsgroup
|         (error "No group name entered"))
|        (or (gnus-active to-newsgroup)
| -	  (gnus-activate-group to-newsgroup)
| +	  (gnus-activate-group to-newsgroup nil nil
| +			       (gnus-group-method to-newsgroup))
|           (if (gnus-y-or-n-p (format "No such group: %s.  Create it? "
|                                      to-newsgroup))
|               (or (and (gnus-request-create-group
| -			to-newsgroup (gnus-group-name-to-method to-newsgroup))
| +			to-newsgroup (gnus-group-method to-newsgroup))
|                        (gnus-activate-group
|                         to-newsgroup nil nil
| -			(gnus-group-name-to-method to-newsgroup))
| +			(gnus-group-method to-newsgroup))
|                        (gnus-subscribe-group to-newsgroup))
|                   (error "Couldn't create group %s" to-newsgroup)))
|           (error "No such group: %s" to-newsgroup)))
`-----




             reply	other threads:[~2000-04-20 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-20 20:20 Chris Brierley [this message]
2000-04-20 21:30 ` Lars Magne Ingebrigtsen
2000-04-21 14:24   ` Chris Brierley

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=wkln28bk2t.fsf@pobox.com \
    --to=brierley@pobox.com \
    /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).