Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Cc: Dave Abrahams <dave@boostpro.com>
Subject: [PATCH 0/5] *** Resubmit: Warping via the registry ***
Date: Thu, 15 Mar 2012 14:23:08 -0400	[thread overview]
Message-ID: <1331835793-70228-1-git-send-email-dave@boostpro.com> (raw)

Note: I submitted this patch series back in October
(http://permalink.gmane.org/gmane.emacs.gnus.general/80250).  It still
applies perfectly, but I rebased just in case.  I'd really appreciate
it if this series could get some attention.  Further explanation of
the motivation for this series is in
http://article.gmane.org/gmane.emacs.gnus.general/80277. Thanks!


This patch series implements the ability to warp to a message via
information stored in the Gnus registry.  From a user's point-of-view,
this means that articles brought in from other groups by
gnus-*-refer-* can be used as a jumping-off-point for further
references.  For example, I am using this code to jump to a given
message:

(defun gnus-goto-article (message-id)
  (with-temp-buffer
    (erase-buffer)
    ;; Insert dummy article
    (insert (format "From nobody Tue Sep 13 22:05:34 2011\n\n"))
    (gnus-group-read-ephemeral-group
     message-id
     `(nndoc ,message-id
             (nndoc-address ,(current-buffer))
             (nndoc-article-type mbox))
     :activate
     (cons (current-buffer) gnus-current-window-configuration)
     (not :request-only)
     '(-1) ; :select-articles
     (not :parameters)
     0     ; :number
     )
    (gnus-summary-refer-article message-id)
    ))

Before applying this patch series, I could not get to the whole thread
with `A T' because Gnus was unable to warp to the article in its
original group.

How it works
------------

Each time a message is fetched from a backend, its group is noted in
the registry.  Warping now consults the backend of the current group,
and if that fails, tries warping to the article in each group stored
for it in the registry until one succeeds.

Dave Abrahams (5):
  Allow gnus-summary-insert-subject to work in empty groups.
  Record information in the registry about each article retrieved
  Add `gnus-select-group-with-message-id'
  Add `gnus-try-warping-via-registry()'
  Enable registry-warping as a fallback if warping via the current
    backend fails.

 lisp/gnus-int.el |  101 ++++++++++++++++++++++++++++++++++++++++++++++++++++--
 lisp/gnus-sum.el |   11 +++++-
 2 files changed, 107 insertions(+), 5 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-03-15 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 18:23 Dave Abrahams [this message]
2012-03-15 18:23 ` [PATCH 1/5] Allow gnus-summary-insert-subject to work in empty groups Dave Abrahams
2012-03-15 18:23 ` [PATCH 2/5] Record information in the registry about each article retrieved Dave Abrahams
2012-03-15 18:23 ` [PATCH 3/5] Add `gnus-select-group-with-message-id' Dave Abrahams
2012-03-15 18:23 ` [PATCH 4/5] Add `gnus-try-warping-via-registry()' Dave Abrahams
2012-03-15 18:23 ` [PATCH 5/5] Enable registry-warping as a fallback if warping via the current backend fails Dave Abrahams
2012-03-19 17:05 ` [PATCH 0/5] *** Resubmit: Warping via the registry *** Ted Zlatanov
2012-03-22 20:59 ` 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=1331835793-70228-1-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).