From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: A T does not work in nnimap
Date: Sat, 16 Oct 2010 08:58:06 -0400 [thread overview]
Message-ID: <87mxqepa5d.fsf@andy.bu.edu> (raw)
In-Reply-To: <87pqvb71nt.fsf@keller.adm.naquadah.org>
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
Umm, apparently you have to DO something with headers once you've
retrieved them :)
This is a small bug fix which solves my problem that 'A T' would
sometimes fail to show the thread.
Regards,
Andy
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-sum fix --]
[-- Type: text/x-diff, Size: 661 bytes --]
diff --git a/lisp/gnus-sum.el b/lisp/gnus-sum.el
index c50d8aa..39f6314 100644
--- a/lisp/gnus-sum.el
+++ b/lisp/gnus-sum.el
@@ -8834,7 +8834,11 @@ variable."
(limit (if limit (prefix-numeric-value limit)
gnus-refer-thread-limit)))
(if (gnus-check-backend-function 'request-thread gnus-newsgroup-name)
- (gnus-request-thread id)
+ (setq gnus-newsgroup-headers
+ (gnus-merge 'list
+ gnus-newsgroup-headers
+ (gnus-request-thread id)
+ 'gnus-article-sort-by-number))
(unless (eq gnus-fetch-old-headers 'invisible)
(gnus-message 5 "Fetching headers for %s..." gnus-newsgroup-name)
;; Retrieve the headers and read them in.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: changes --]
[-- Type: text/x-diff, Size: 407 bytes --]
diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 1a66ec9..35a9de4 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2010-10-16 Andrew Cohen <cohen@andy.bu.edu>
+
+ * gnus-sum.el (gnus-summary-refer-thread): Bug fix. Add the thread
+ headers to gnus-newsgroup-headers.
+
2010-10-15 Andrew Cohen <cohen@andy.bu.edu>
* gnus-sum.el (gnus-summary-refer-thread): unconditionally ignore
next prev parent reply other threads:[~2010-10-16 12:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 11:00 Julien Danjou
2010-10-07 18:13 ` Lars Magne Ingebrigtsen
2010-10-12 13:28 ` Julien Danjou
2010-10-12 13:50 ` Lars Magne Ingebrigtsen
2010-10-12 14:18 ` Julien Danjou
2010-10-12 14:43 ` Andrew Cohen
2010-10-12 23:43 ` Andrew Cohen
2010-10-13 13:55 ` Julien Danjou
2010-10-13 15:30 ` Andrew Cohen
2010-10-13 15:42 ` Julien Danjou
2010-10-13 17:21 ` Lars Magne Ingebrigtsen
2010-10-13 17:56 ` Andrew Cohen
2010-10-13 18:29 ` Lars Magne Ingebrigtsen
2010-10-13 20:59 ` Andrew Cohen
2010-10-13 21:11 ` Lars Magne Ingebrigtsen
2010-10-13 21:30 ` Andrew Cohen
2010-10-13 21:37 ` Lars Magne Ingebrigtsen
2010-10-13 21:59 ` Andrew Cohen
2010-10-13 22:06 ` Lars Magne Ingebrigtsen
2010-10-14 0:38 ` Andrew Cohen
2010-10-14 12:57 ` Andrew Cohen
2010-10-14 18:00 ` Lars Magne Ingebrigtsen
2010-10-14 18:45 ` Andrew Cohen
2010-10-14 19:02 ` Lars Magne Ingebrigtsen
2010-10-15 11:02 ` Julien Danjou
2010-10-15 11:24 ` Andrew Cohen
2010-10-15 11:29 ` Julien Danjou
2010-10-15 11:53 ` Steinar Bang
2010-10-15 12:01 ` Julien Danjou
2010-10-15 12:00 ` Andrew Cohen
2010-10-15 12:06 ` Julien Danjou
2010-10-15 12:17 ` Andrew Cohen
2010-10-15 12:26 ` Andrew Cohen
2010-10-15 18:26 ` Julien Danjou
2010-10-16 12:58 ` Andrew Cohen [this message]
2010-10-16 18:16 ` Lars Magne Ingebrigtsen
2010-10-15 14:03 ` Lars Magne Ingebrigtsen
2010-10-15 12:11 ` Andrew Cohen
2010-10-15 12:28 ` Julien Danjou
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=87mxqepa5d.fsf@andy.bu.edu \
--to=cohen@andy.bu.edu \
--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).