Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: ding@gnus.org
Subject: Re: Proposal: gnus-refer-article
Date: Thu, 01 Aug 2013 18:15:06 +0200	[thread overview]
Message-ID: <m31u6dbd6d.fsf@stories.gnus.org> (raw)
In-Reply-To: <m2lia3r7if.fsf@boostpro.com> (Dave Abrahams's message of "Sun, 03 Mar 2013 22:42:00 -0800")

Dave Abrahams <dave@boostpro.com> writes:

> I propose the following code for inclusion in Gnus.  It defines a new
> function, `gnus-refer-article', which is just like
> `gnus-summary-refer-article', but can be invoked outside the summary
> buffer.  The article will appear in a new buffer.
>
> With this, I can store links to articles/messages I want to deal with in
> my TODO list and jump to them at any time.  If I want to see the article
> in context of its entire thread, that's just an `A T' away.

That's a good idea, but there are some things I don't quite understand
in the implementation.

> ;; We'll need to create a dummy group from which we can use
> ;; gnus-summary-refer-article.  An nndoc group almost works for that
> ;; purpose, but nndoc is a non-virtual backend, and warping (which
> ;; gnus-summary-refer-article needs in order to find the article) only
> ;; works in virtual groups.  Therefore, we derive a new virtual
> ;; backend from nndoc and use that instead.

Wouldn't it make sense to make warping work in nndoc groups instead, and
then we wouldn't need another backend?

-- 
(domestic pets only, the antidote for overdose, milk.)
  No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php



  reply	other threads:[~2013-08-01 16:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  6:42 Dave Abrahams
2013-08-01 16:15 ` Lars Magne Ingebrigtsen [this message]
2013-08-02 14:05   ` Dave Abrahams
2013-08-02 14:13     ` Lars Magne Ingebrigtsen
2013-08-02 15:00       ` Dave Abrahams
2013-08-03 11:24         ` Lars Magne Ingebrigtsen
2013-08-03 16:24           ` Dave Abrahams
2013-08-05  2:16             ` Lars Magne Ingebrigtsen
2013-08-05  5:10               ` Dave Abrahams
2013-09-29  2:12               ` Dave Abrahams
2013-10-03  3:27                 ` Eric Abrahamsen
2014-02-01  0:00                 ` Lars 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=m31u6dbd6d.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=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).