From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnir, gnus-goto-article and such
Date: Wed, 28 Sep 2011 19:32:37 -0500 [thread overview]
Message-ID: <878vp8nq6y.fsf@lifelogs.com> (raw)
In-Reply-To: <m2hb3whh16.fsf@pluto.luannocracy.com>
On Wed, 28 Sep 2011 10:34:45 -0400 Dave Abrahams <dave@boostpro.com> wrote:
DA> on Tue Sep 27 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:
>> Er, you can split to the reference parent,
DA> I don't use client-side splitting, so I guess that doesn't make much
DA> difference to me, but I guess it might for others.
Yes, it makes a huge difference.
>> or by subject, or by sender?
DA> You can't split by subject or sender without the registry?! You're
DA> kidding, right? Like I said, I never ask Gnus to shuffle mail into
DA> different folders for me but that seems pretty basic.
No, I mean it will split to the same group as other articles with the
same subject or sender. So if I put your mails in "dave" it will figure
out it should keep putting new ones in there.
>> It lets the user keep registry marks? Are those not exploitative
>> enough?
DA> What's a user going to *do* with registry marks? That's another tool
DA> whose real utility escapes me.
It lets the user define any marks they want, without reconfiguring Gnus
and without storing them in the newsrc.eld, by message-ID and not
article number.
>> (defun gnus-registry-handle-action (id from to subject sender
>> &optional recipients)
DA> Umm, sorry. That function isn't documented. How do I use it? How
DA> would I get the group that gnus-summary-refer-article finds the message
DA> in into the registry? I don't even see a parameter for group.
id = message ID, a string
from = source group, nil in your case for a new article
to = destination group, your group
subject, sender, receipients = strings
The group name is fully qualified IIRC.
Ted
next prev parent reply other threads:[~2011-09-29 0:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 18:24 Dave Abrahams
2011-09-16 15:05 ` gnus-warp-to-article (was: nnir, gnus-goto-article and such) Dave Abrahams
2011-09-21 18:03 ` nnir, gnus-goto-article and such Lars Magne Ingebrigtsen
2011-09-21 21:16 ` John Wiegley
2011-09-22 13:01 ` Andrew Cohen
2011-09-26 19:17 ` Lars Magne Ingebrigtsen
2011-09-26 20:46 ` Dave Abrahams
2011-09-27 7:04 ` John Wiegley
2011-09-27 15:36 ` Dave Abrahams
2011-09-26 20:01 ` Dave Abrahams
2011-09-26 21:35 ` Ted Zlatanov
2011-09-27 15:35 ` Dave Abrahams
2011-09-27 21:12 ` Ted Zlatanov
2011-09-28 14:34 ` Dave Abrahams
2011-09-29 0:32 ` Ted Zlatanov [this message]
2011-09-29 1:19 ` Dave Abrahams
2011-09-29 2:06 ` Dave Abrahams
2011-09-29 8:27 ` Ted Zlatanov
2011-09-29 13:40 ` Dave Abrahams
2011-09-29 14:00 ` Ted Zlatanov
2011-09-29 14:40 ` Dave Abrahams
2011-09-29 14:58 ` Ted Zlatanov
2011-09-29 20:04 ` Dave Abrahams
2011-09-29 23:40 ` Ted Zlatanov
2011-09-29 8:22 ` Ted Zlatanov
2011-09-27 16:04 ` Dave Abrahams
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=878vp8nq6y.fsf@lifelogs.com \
--to=tzz@lifelogs.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).