From: Norbert Koch <viteno@xemacs.org>
Subject: Re: Gnus registry woes
Date: Tue, 29 Jun 2004 22:51:23 +0200 [thread overview]
Message-ID: <vzu0wu9jg4.fsf@redqueen.ath.cx> (raw)
In-Reply-To: <4nsmce5iol.fsf@lifelogs.com> (Ted Zlatanov's message of "29 Jun 2004 14:21:30 -0400")
"Ted Zlatanov" <tzz@lifelogs.com> writes:
> I would guess the natnump error, which I have never seen before, is
> coming from an invalid mtime. Can you trace the error deeper with
> (debug) statements inside the lambda function above? Alternatively,
> can you send me your registry file, if the error is repeatable from
> it?
I think the problem is there *is* no registry file, yet. Should I
create it (empty)?
I can try to step down expressions, though.
Thanks,
norbert.
next prev parent reply other threads:[~2004-06-29 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 9:21 Norbert Koch
2004-06-29 18:21 ` Ted Zlatanov
2004-06-29 20:51 ` Norbert Koch [this message]
2004-06-30 15:15 ` Norbert Koch
2004-06-30 18:00 ` Ted Zlatanov
2004-07-01 5:56 ` Norbert Koch
2004-06-30 17:52 ` Ted Zlatanov
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=vzu0wu9jg4.fsf@redqueen.ath.cx \
--to=viteno@xemacs.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).