From: Ted Zlatanov <tzz@lifelogs.com>
To: Bastien <bzg@altern.org>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: gnus-registry.el problem
Date: Thu, 17 Jan 2008 23:02:46 -0600 [thread overview]
Message-ID: <m2zlv3lo95.fsf@lifelogs.com> (raw)
In-Reply-To: <87prw0ezwm.fsf@bzg.ath.cx>
To disable the trimming, which was the problem, just
(setq gnus-registry-max-entries nil)
in general. That makes gnus-registry-trim just return the full list.
I think I found the problem: I confused concat with append in the code I
added recently. Try the latest from CVS. I'm not sure why it worked
for me when I tested it; sorry for the inconvenience. Let me know if it
works for you.
Ted
next prev parent reply other threads:[~2008-01-18 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m0r6gujtpi.fsf@gmail.com>
[not found] ` <mailman.5812.1199695477.18990.info-gnus-english@gnu.org>
[not found] ` <86myrhr2jc.fsf@lifelogs.com>
2008-01-17 13:40 ` tags, keywords, annotations Bastien
2008-01-17 14:17 ` Ted Zlatanov
2008-01-18 0:32 ` gnus-registry.el problem (was: tags, keywords, annotations) Bastien
2008-01-18 5:02 ` Ted Zlatanov [this message]
2008-01-18 14:22 ` gnus-registry.el problem Bastien
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=m2zlv3lo95.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=bzg@altern.org \
--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).