Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Agent categories gone.
Date: Tue, 04 Mar 2003 16:29:02 -0600	[thread overview]
Message-ID: <u1y1mlqa9.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <86smu3z2d2.fsf@i3d.home>

Robert Epprecht <epprecht@solnet.ch> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Hmmm.... What's the value of gnus-agent-directory just before you
>> executed (gnus-category-read)?
>
> gnus-agent-directory's value is "~/News/agent/"
>
>> 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))
>
> This gives a *different* result (formatted by hand):
>
> ((header (agent-predicate . false))
>  (all (agent-predicate . true)
>   (agent-groups "comp.lang.forth" "gnu.emacs.sources"))
>  (default (agent-predicate . high)
>  (agent-score-file . file)))
>
>> At this point, you should have been thrown into the debug buffer.
> no
>
> Strange, very strange. This looks to me as if the compiled gnus-agent.elc
> file would not correspond to the gnus-agent.el file. Hmm

and I concur.  The preceeding results are exactly what we would hope to see.


> cd /usr/local/gnus
> ./configure
>
> one output line makes me wonder if things go right:
> checking where .elc files should go... $(datadir)/emacs/site-lisp
>
> make
>
> Despite the line shown above the *.elc files in /usr/local/gnus/lisp/
> do get rewritten.

I actually have the misfortune of working on a MS box.  It's been
years since I worked with the configure script.  Does ./configure
delete all of the .elc files?  If it doesn't, try deleting all of the
gnus *.elc files then run make.

>
> restart emacs and gnus
> Same result as before: Different output of (gnus-category-read) before
> and after loading gnus-agent.el. I have double checked gnus-agent-directory.
> It is the same in both cases.
>
> load-path's value is  ("/usr/local/gnus/lisp" ... )
> ls -l /usr/local/gnus/lisp/gnus-agent.el*
> [ ... ]   128524 Mar  4 06:10 /usr/local/gnus/lisp/gnus-agent.el
> [ ... ]    93531 Mar  4 14:03 /usr/local/gnus/lisp/gnus-agent.elc
>
> I don't understand what's happening here.

same here.

You could try debugging the compiled code.  You'll only be able to see
function calls but that may be enough.  For example, after returning
from nnheader-insert-file-contents, the current buffer should contain
the text in your categories file.  Even more important, I believe that
the first read statement is erroring so you should see the execution
stack unwind up to the ignore-errors form.

If you still have problems, I can create a new version of
gnus-category-read that prints a message before every statement.
Hopefully, that would help us isolate the problem to a single
statement.

Kevin




  reply	other threads:[~2003-03-04 22:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 17:22 Robert Epprecht
2003-03-03 17:50 ` Kevin Greiner
2003-03-03 18:09   ` Robert Epprecht
2003-03-03 19:13   ` David S Goldberg
2003-03-03 19:56     ` Robert Epprecht
2003-03-03 22:11       ` Kevin Greiner
2003-03-04  5:22         ` Robert Epprecht
2003-03-04  5:51           ` Kevin Greiner
2003-03-04 13:29             ` Robert Epprecht
2003-03-04 22:29               ` Kevin Greiner [this message]
2003-03-05 15:35                 ` Robert Epprecht
2003-03-05 17:18                   ` Kevin Greiner
2003-03-05 17:34                     ` David S Goldberg
2003-03-05 20:20                       ` Kai Großjohann
2003-03-05 18:35                     ` Robert Epprecht
2003-03-06  6:55                       ` R e: " Kevin Greiner
2003-03-06 13:22                         ` Robert Epprecht
2003-03-06 15:46                           ` Kevin Greiner
2003-03-06 19:01                             ` Robert Epprecht

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=u1y1mlqa9.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).