Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gnus-registry issue ?
Date: Sat, 26 Jul 2003 10:31:11 -0400	[thread overview]
Message-ID: <4nbrvhe4wg.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <plop87llulohui.fsf@gnu-rox.org> (Xavier Maillard's message of "Sat, 26 Jul 2003 09:41:25 +0200")

On Sat, 26 Jul 2003, zedek@gnu-rox.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>>  Strange, your registry variable (gnus-registry-hashtb) is nil.
>>  Maybe you are setting it somewhere, customized perhaps?  Normally
>>  it will get set up as a hashtable when you load gnus-registry.el.
> 
> I didn't set it up. I just did what you wrote in your previous
> message and that's it.
> 
> FYI here it is after my latest g-g-g-n-n :
> 
> ,----[ C-h v gnus-registry-hashtb RET ]
> | gnus-registry-hashtb's value is 
> | #<hash-table 'equal nil 9410/13824 0x9346af0>
> | 
> | *The article registry by Message ID.
> | 
> | Defined in `gnus-registry'.
> `----

Well, this function is failing in gnus-registry.el:

(defun gnus-registry-group-count (id)
  "Get the number of groups of a message, based on the message ID."
  (let ((trail (gethash id gnus-registry-hashtb)))
    (if (and trail (listp trail))
    (apply '+ (mapcar (lambda (x) (if (stringp x) 1 0)) trail))
      0)))

and it's failing when it tries to get the id from the
gnus-registry-hashtb, which is nil in the stack trace you sent me.

I think I see the problem.  gnus-registry-read must be called so the
gnus-registry-hashtb variable is initialized (the
gnus-registry-install variable has to be set for that to happen, and
you must read the newsrc).  Somehow one of the two things didn't
happen for you in sequence when you did the stack trace.  I just put
an explicit gnus-registry-read in the gnus-registry.el loading when
gnus-registry-install is set, that should take care of any possible
uninitialized registry variable cases.  See the latest Gnus CVS and
let me know if you have any more problem.

Thanks
Ted



      reply	other threads:[~2003-07-26 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18  6:08 Xavier Maillard
2003-07-21 15:36 ` Ted Zlatanov
2003-07-22 23:31   ` Xavier Maillard
2003-07-23 14:46     ` Ted Zlatanov
2003-07-24  6:22       ` Xavier Maillard
2003-07-25 19:16         ` Ted Zlatanov
2003-07-26  7:41           ` Xavier Maillard
2003-07-26 14:31             ` Ted Zlatanov [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=4nbrvhe4wg.fsf@lockgroove.bwh.harvard.edu \
    --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).