From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnir and move
Date: Tue, 14 Dec 2010 17:36:35 -0600 [thread overview]
Message-ID: <877hfclyf0.fsf@lifelogs.com> (raw)
In-Reply-To: <87sjyhcfv1.fsf@andy.bu.edu>
On Wed, 01 Dec 2010 17:01:22 -0500 Andrew Cohen <cohen@andy.bu.edu> wrote:
>>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Andrew Cohen <cohen@andy.bu.edu> writes:
>>> Add gnus-summary-article-delete-hook (and -move-hook) to
>>> gnus-summary-local-variables (these are the hooks the registry
>>> uses to do its thing). Then nnir can override them in nnir groups
>>> and deal with the registry stuff itself. This should be really
>>> easy and means all the nnir-specific stuff is confined to
>>> nnir.el.
Lars> Sounds good to me, I think.
AC> OK, I just pushed it. And, I just noticed that I foolishly pushed
AC> hundreds of lines or reindented code since I removed a let. The
AC> substantive changes are a couple dozen lines or so.
Haha, I'm not the only one to do it :)
Thanks for working on this and all the other nnir.el code. It has
improved Gnus search immensely.
Ted
next prev parent reply other threads:[~2010-12-14 23:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 14:07 Richard Riley
2010-10-31 17:18 ` Lars Magne Ingebrigtsen
2010-11-01 4:20 ` Richard Riley
2010-11-01 12:04 ` Andrew Cohen
2010-11-01 12:08 ` Lars Magne Ingebrigtsen
2010-11-01 12:13 ` Andrew Cohen
2010-11-01 14:28 ` Andrew Cohen
2010-11-01 14:51 ` Andrew Cohen
2010-11-09 22:05 ` Ted Zlatanov
2010-11-10 16:40 ` Andrew Cohen
2010-11-10 16:55 ` Ted Zlatanov
2010-11-10 18:42 ` Andrew Cohen
2010-11-10 18:54 ` Ted Zlatanov
2010-11-10 19:09 ` Andrew Cohen
2010-11-15 2:40 ` Katsumi Yamaoka
2010-11-15 2:53 ` Andrew Cohen
2010-12-01 14:13 ` Andrew Cohen
2010-12-01 17:01 ` Lars Magne Ingebrigtsen
2010-12-01 17:47 ` Andrew Cohen
2010-12-01 17:50 ` Lars Magne Ingebrigtsen
2010-12-01 22:01 ` Andrew Cohen
2010-12-14 23:36 ` Ted Zlatanov [this message]
2010-11-03 1:05 Andrew Cohen
2010-11-03 12:17 ` Richard Riley
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=877hfclyf0.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).