Gnus development mailing list
 help / color / mirror / Atom feed
From: Tibor Simko <tibor.simko@cern.ch>
To: ding@gnus.org
Subject: Re: latest sources do not client-split IMAP anymore
Date: Wed, 15 Dec 2010 03:33:04 +0100	[thread overview]
Message-ID: <87fwtz4vfj.fsf@pcuds33.cern.ch> (raw)
In-Reply-To: <m3lj3sm1jj.fsf@quimbies.gnus.org>

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

On Tue, 14 Dec 2010, Lars Magne Ingebrigtsen wrote:
> It seems to work for me, and I can't remember touching any
> nnimap-relevant code the last few days...

It's due to recent changes in `gnus-setup-news'.  The attached patch
fixes things for me.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnus-start.el-gnus-setup-news-add-back-gnus-read-act.patch --]
[-- Type: text/x-diff, Size: 1444 bytes --]

From 9a6117fb06879598a9171abe4f21762dffc3eae4 Mon Sep 17 00:00:00 2001
From: Tibor Simko <tibor.simko@cern.ch>
Date: Wed, 15 Dec 2010 02:59:09 +0100
Subject: [PATCH] gnus-start.el (gnus-setup-news): add back gnus-read-active-file parts

* Add back parts of code removed in cc7d0e0 related to gnus-read-active-file;
  this fixes the problem of IMAP client-side splitting that was working fine
  in my setup up to be87151 but stopped working after 3595cdc.
---
 lisp/gnus-start.el |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/lisp/gnus-start.el b/lisp/gnus-start.el
index d9e4327..194bfc1 100644
--- a/lisp/gnus-start.el
+++ b/lisp/gnus-start.el
@@ -995,8 +995,17 @@ If LEVEL is non-nil, the news will be set up at level LEVEL."
     (when (or (null gnus-read-active-file)
 	      (eq gnus-read-active-file 'some))
       (gnus-update-active-hashtb-from-killed))
+
+    ;; Read the active file and create `gnus-active-hashtb'.
+    ;; If `gnus-read-active-file' is nil, then we just create an empty
+    ;; hash table.  The partial filling out of the hash table will be
+    ;; done in `gnus-get-unread-articles'.
+    (and gnus-read-active-file
+         (not level)
+         (gnus-read-active-file nil dont-connect))
     (unless gnus-active-hashtb
       (setq gnus-active-hashtb (gnus-make-hashtable 4096)))
+
     ;; Initialize the cache.
     (when gnus-use-cache
       (gnus-cache-open))
-- 
1.7.2.3


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


Best regards
-- 
Tibor Simko

  reply	other threads:[~2010-12-15  2:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 18:33 Tibor Simko
2010-12-14 22:29 ` Lars Magne Ingebrigtsen
2010-12-15  2:33   ` Tibor Simko [this message]
2010-12-15 19:24     ` Lars Magne Ingebrigtsen
2010-12-15 21:11       ` Tibor Simko
2010-12-16 16:13         ` Lars Magne Ingebrigtsen
2010-12-16 17:21           ` Tibor Simko
2010-12-16 17:25             ` Lars Magne Ingebrigtsen
2010-12-16 21:39               ` Tibor Simko
2010-12-18 20:19                 ` Richard Riley
2010-12-20 23:55                   ` Tibor Simko

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=87fwtz4vfj.fsf@pcuds33.cern.ch \
    --to=tibor.simko@cern.ch \
    --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).