Gnus development mailing list
 help / color / mirror / Atom feed
From: Andy Moreton <andrewjmoreton@gmail.com>
To: ding@gnus.org
Subject: Re: Patch Series: Warping via the registry
Date: Wed, 12 Oct 2011 16:04:06 +0100	[thread overview]
Message-ID: <vz14nzegsk9.fsf@gmail.com> (raw)
In-Reply-To: <m2ty7g1euu.fsf@pluto.luannocracy.com>

On Tue 11 Oct 2011, Dave Abrahams wrote:

> on Mon Oct 10 2011, Andy Moreton <andrewjmoreton-AT-gmail.com> wrote:
>
>> On Sun 09 Oct 2011, Dave Abrahams wrote:
>>
>>> 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.
>>
>> You have invented yet another term to confuse gnus users in this patch
>> series, but have not defined what "warp" means.
>
> If you're complaining about the term "warp," I didn't invent it (and
> probably wouldn't have thought of a term that cute).
>
> ,----[ (info "(gnus)Basic Usage") ]
> |    The `nnir' group made in this way is an `ephemeral' group, and some
> | changes are not permanent: aside from reading, moving, and deleting,
> | you can't act on the original article. But there is an alternative: you
> | can _warp_ to the original group for the article on the current line
> | with `A W', aka `gnus-warp-to-article'. Even better, the function
> | `gnus-summary-refer-thread', bound by default in summary buffers to `A
> | T', will first warp to the original group before it works its magic and
> | includes all the articles in the thread. From here you can read, move
> | and delete articles, but also copy them, alter article marks, whatever.
> | Go nuts.
> `----

Ahh, I see. Another part of manual which uses terms without defining
them adequately...

>> Please add some documentation to explain the use of this new feature. If
>> you can do so *without* defining new terminology, all the better.
>
> I can do some explaining here, but I'm afraid it wouldn't fit into the
> manual as is.  I hope this will be helpful.

I wasn't making any judgement on the quality or utility of your patch -
merely trying to nudge you towards also patching the manual :-)

> This patch series makes it possible to initiate a warp from any group,
> which in turn makes it possible to follow threads starting from
> ephemeral groups other than an nnir group.
>
> Why would you want to do that?  The `gnus-goto-article' function I
> posted in the series' introductory email allows me, given just a
> Message-ID, to jump into a buffer containing that message, regardless of
> which group or server the message came from (set up
> gnus-refer-article-method to enable that).  That's awesomely powerful,
> but without the patch series, I can't get from that article to its
> entire thread.  With the patch series, I can, because gnus will warp me
> to the group from which gnus-summary-refer-article plucked it.
>
> If you want to know why I want to fetch articles by Message-ID in the
> first place, it's because I store references to them in Org files, and
> need to be able to jump from the Org item to the message.

This sounds like a useful feature. Please try to add your explanation or
something similar to the manual, as it would make useful docuemntation.

     AndyM




      parent reply	other threads:[~2011-10-12 15:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09  4:11 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 ` [PATCH 3/6] Add `gnus-select-group-with-message-id' Dave Abrahams
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     ` Andy Moreton [this message]

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=vz14nzegsk9.fsf@gmail.com \
    --to=andrewjmoreton@gmail.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).