From: Nicolas Kowalski <Nicolas.Kowalski@imag.fr>
Subject: Re: Limit summary to participant
Date: Wed, 02 Oct 2002 09:19:31 +0200 [thread overview]
Message-ID: <vqoit0lwbng.fsf@astazou.imag.fr> (raw)
In-Reply-To: <87ofad4h49.fsf@uwo.ca> (Dan Christensen's message of "Wed, 02 Oct 2002 00:08:54 -0400")
Dan Christensen <jdc@uwo.ca> writes:
> Nicolas Kowalski <Nicolas.Kowalski@imag.fr> writes:
>
>> What hook is the best for this ? If I use :
>>
>> (add-hook 'gnus-summary-prepare-hook
>> (lambda ()(gnus-summary-limit-to-age 7 t)))
>>
>> ...it turns into infinite loop :-(.
>
> You should use gnus-summary-prepared-hook, which only runs the
> first time a summary buffer is produced. Also, this allows you
> to use '/ w' to pop this limit.
This works well :-).
Thanks for the tip.
--
Nicolas
next prev parent reply other threads:[~2002-10-02 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 9:02 Nicolas Kowalski
2002-09-30 10:01 ` Kai Großjohann
2002-09-30 11:05 ` Nicolas Kowalski
2002-09-30 13:52 ` Kai Großjohann
2002-09-30 13:58 ` Nicolas Kowalski
2002-10-02 4:08 ` Dan Christensen
2002-10-02 7:19 ` Nicolas Kowalski [this message]
[not found] ` <hhwup3sry1.fsf@blah.pl>
2002-09-30 13:51 ` Kai Großjohann
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=vqoit0lwbng.fsf@astazou.imag.fr \
--to=nicolas.kowalski@imag.fr \
/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).