From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Cc: Dave Abrahams <dave@boostpro.com>
Subject: [PATCH 3/6] Add `gnus-select-group-with-message-id'
Date: Sun, 9 Oct 2011 00:11:24 -0400 [thread overview]
Message-ID: <1318133487-45386-4-git-send-email-dave@boostpro.com> (raw)
In-Reply-To: <1318133487-45386-1-git-send-email-dave@boostpro.com>
---
lisp/gnus-int.el | 43 +++++++++++++++++++++++++++++++++++++++++++
1 files changed, 43 insertions(+), 0 deletions(-)
diff --git a/lisp/gnus-int.el b/lisp/gnus-int.el
index 2e10263..048f442 100644
--- a/lisp/gnus-int.el
+++ b/lisp/gnus-int.el
@@ -531,6 +531,49 @@ If BUFFER, insert the article in that group."
header
(gnus-group-real-name group))))
+(defun gnus-select-group-with-message-id (group message-id)
+ "Activate and select GROUP with the given MESSAGE-ID selected.
+Returns the article number of the message.
+
+If GROUP is not already selected, the message will be the only one in
+the group's summary.
+"
+ ;; TODO: is there a way to know at this point whether the group will
+ ;; be newly-selected? If so we could clean up the logic at the end
+ ;;
+ ;; save the new group's display parameter, if any, so we
+ ;; can replace it temporarily with zero.
+ (let ((saved-display
+ (gnus-group-get-parameter group 'display :allow-list)))
+
+ ;; Tell gnus we really don't want any articles
+ (gnus-group-set-parameter group 'display 0)
+
+ (unwind-protect
+ (gnus-summary-read-group-1
+ group (not :show-all) :no-article (not :kill-buffer)
+ ;; The combination of no-display and this dummy list of
+ ;; articles to select somehow makes it possible to open a
+ ;; group with no articles in it. Black magic.
+ :no-display '(-1); select-articles
+ )
+ ;; Restore the new group's display parameter
+ (gnus-group-set-parameter group 'display saved-display)))
+
+ ;; The summary buffer was suppressed by :no-display above.
+ ;; Create it now and insert the message
+ (let ((group-is-new (gnus-summary-setup-buffer group)))
+ (condition-case err
+ (let ((article-number
+ (gnus-summary-insert-subject message-id)))
+ (unless article-number
+ (signal 'error "message-id not in group"))
+ (gnus-summary-select-article nil nil nil article-number)
+ article-number)
+ ;; Clean up the new summary and propagate the error
+ (error (when group-is-new (gnus-summary-exit))
+ (apply 'signal err)))))
+
(defun gnus-warp-to-article ()
"Warps from an article in a virtual group to the article in its
real group. Does nothing on a real group."
--
1.7.6.1
next prev parent reply other threads:[~2011-10-09 4:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 4:11 Patch Series: Warping via the registry Dave Abrahams
2011-10-09 4:11 ` [PATCH 1/6] Allow gnus-summary-insert-subject to work in empty groups Dave Abrahams
2011-10-09 4:11 ` [PATCH 2/6] Record information in the registry about each article retrieved Dave Abrahams
2011-10-09 4:11 ` Dave Abrahams [this message]
2011-10-09 4:11 ` [PATCH 4/6] Add `gnus-try-warping-via-registry()' Dave Abrahams
2011-10-09 4:11 ` [PATCH 5/6] Enable registry-warping as a fallback if warping via the current backend fails Dave Abrahams
2011-10-09 4:11 ` [PATCH 6/6] Use `gnus-registry-enabled' instead of `gnus-registry-install' Dave Abrahams
2011-10-10 23:09 ` Patch Series: Warping via the registry Andy Moreton
2011-10-11 1:44 ` Dave Abrahams
2011-10-12 14:48 ` *bump* (was: Patch Series: Warping via the registry) Dave Abrahams
2011-10-12 23:38 ` *bump* Ted Zlatanov
2011-10-16 12:02 ` *bump* again Dave Abrahams
2011-11-03 22:56 ` Lars Magne Ingebrigtsen
2011-11-04 0:23 ` Dave Abrahams
2011-11-04 8:36 ` Steinar Bang
2011-11-04 11:26 ` Steinar Bang
2011-11-04 12:35 ` Gnus Git branching strategy for Emacs sync (was: *bump* again) Ted Zlatanov
2011-11-04 15:30 ` *bump* again Dave Abrahams
2011-11-04 16:07 ` Steinar Bang
2011-11-05 5:13 ` Dave Abrahams
2011-11-05 10:09 ` John Wiegley
2011-11-04 12:26 ` Ted Zlatanov
2011-10-12 15:04 ` Patch Series: Warping via the registry Andy Moreton
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=1318133487-45386-4-git-send-email-dave@boostpro.com \
--to=dave@boostpro.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).