Re: Agent categories gone.

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Robert Epprecht <epprecht@solnet.ch> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> M-: (gnus-category-read) 
>
> ((default (agent-predicate . false)))
>
> Robert

Excellent.  It appears that you're getting some sort of I/O when the
agent tries to read your file.  

The detailed explanation is as follows.  If you look at the
implementation of gnus-category-read, you will see that the last line
reads in part: (gnus-agent-cat-make 'default).  This statement is
generating the list that is being returned.  This statement is the
second cause of an or-statement so the first cause, the entire
(with-temp-buffer ...) statement, returned nil.

Hmmm.... What's the value of gnus-agent-directory just before you
executed (gnus-category-read)?

If gnus-agent-directory looks OK to you, I'd like you to do the
following.  If you don't mind helping with the debugging that is.

1) Start gnus as usual.
2) Load gnus-agent.el so that gnus-category-read isn't compiled. (M-x
   load-library<RET>gnus-agent.el<RET>)
3) Set debug-on-signal (M-: (setq debug-on-signal t))
4) Execute gnus-category-read (M-: (gnus-category-read))

At this point, you should have been thrown into the debug buffer.
Copy that buffer to a scratch buffer then type the letter c to
continue.  Repeat each time the function stops in the debug buffer.
When you're done, I'd like to see the stack traces.

If the debug buffer isn't displayed, you'll need to step through the
execution to see where it fails.

Kevin