From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nnvirtual counts messages but gives an error
Date: Wed, 04 May 2022 18:53:50 -0700 [thread overview]
Message-ID: <87v8ukoic1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87v8ulyng6.fsf@ecocode.net>
Erik Colson <eco@ecocode.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Can you set `toggle-debug-on-error' to t, trigger the error again,
>> and post the backtrace here?
>
> Here it is:
>
> Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
> gnus-cache-update-active("FASTMAIL/Inbox" 2664 t)
> gnus-cache-articles-in-group("FASTMAIL/Inbox")
> gnus-cache-retrieve-headers((4 5 9 10 11 14 22 23 24 25 26 27 30 32 34 35 38 40 41 43 48 49 51 52 53 54 55 58 60 62 68 69 70 71 73 74 75 76 77 78 79 81 82 83 84 85 86 89 90 92 ...) "FASTMAIL/Inbox" nil)
Let's see...
The `gnus-cache-open' function is called at startup, so long as
`gnus-use-cache is non-nil.
When `gnus-cache-open' is called, it will call `gnus-cache-read-active',
which will always create the hash table in question, one way or the
other. The only way it will not call `gnus-cache-read-active' is if this
test fails to pass:
(or (file-exists-p gnus-cache-directory)
(and gnus-use-cache
(not (eq gnus-use-cache 'passive))))
I'm guessing your `gnus-cache-directory' points to a non-existent
directory? I'm also assuming your `gnus-use-cache' is 'passive.
It's a bit weird, though -- if the directory doesn't exist but
`gnus-use-cache' is non-nil, it seems like Gnus should either create the
directory, or just not attempt to use the cache.
As it is, `gnus-cache-read-active' creates the cache directory, but only
if... it already exists.
next prev parent reply other threads:[~2022-05-05 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 12:51 Erik Colson
2022-05-04 17:10 ` Eric Abrahamsen
2022-05-04 21:53 ` Erik Colson
2022-05-05 1:53 ` Eric Abrahamsen [this message]
2022-05-05 9:59 ` Erik Colson
2022-05-05 15:13 ` Eric Abrahamsen
2022-05-05 18:42 ` Erik Colson
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=87v8ukoic1.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).