From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: Thread limiting
Date: Sat, 27 May 2006 14:38:25 +0200 [thread overview]
Message-ID: <87d5dz8wxq.fsf@baldur.nicundtas.de> (raw)
In-Reply-To: <1148724852.657305.144960@i39g2000cwa.googlegroups.com>
"Guillaume R." <raimondeau@gmail.com> writes:
>> Hm, right. I think the manual assumes a certain familiarity with
>> Emacs.
>
> Yes I suppose you were right so yesterday, I've completed the tutorial
> (a well done one btw)
Yeah, the whole Gnus documentation is a fun read.
>> How do you want to achieve it without a hook?
>
> Hum I dont know elisp (yet!) so I've just write sth like:
> (setq gnus-summary-limit-to-age 30)
> And it does not work...
This cannot work. gnus-summary-limit-to-age is a function, so you have
to call it somewhere. That's where hooks are for.
> I test your hook and it doesn't work too, I've got a strange message
> error:
> "Variable binding depth exceeds max-specpdl-size"
I tested it and get a similar error. (something with max-eval-depth)
> Do you know what does it mean?
Not really. But this one works for me:
(add-hook 'gnus-summary-prepared-hook
(lambda ()
(gnus-summary-limit-to-age 1 t)))
This time its gnus-summary-prepared-hook hook, instead of
gnus-summary-prepare-hook.
Bye,
Tassilo
--
VI VI VI - The Roman Number Of The Beast
prev parent reply other threads:[~2006-05-27 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 11:48 Guillaume R.
2006-05-25 14:07 ` Tassilo Horn
[not found] ` <mailman.2280.1148566098.9609.info-gnus-english@gnu.org>
2006-05-25 14:40 ` Guillaume R.
2006-05-25 16:28 ` Tassilo Horn
[not found] ` <mailman.2288.1148574539.9609.info-gnus-english@gnu.org>
2006-05-26 7:23 ` Guillaume R.
2006-05-26 10:07 ` Tassilo Horn
[not found] ` <mailman.2315.1148638103.9609.info-gnus-english@gnu.org>
2006-05-27 10:14 ` Guillaume R.
2006-05-27 11:41 ` Cor Gest
2006-05-27 12:38 ` Tassilo Horn [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=87d5dz8wxq.fsf@baldur.nicundtas.de \
--to=heimdall@uni-koblenz.de \
/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).