Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Backtrace on agent fetching
Date: Tue, 04 Mar 2003 07:11:41 -0600	[thread overview]
Message-ID: <uznob8eeq.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <84isuzto23.fsf@lucy.is.informatik.uni-duisburg.de>

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> I got a backtrace on agent fetching:
>
> Debugger entered--Lisp error: (wrong-type-argument listp #[nil "À ?" [gnus-agent-read-p] 1])
>   gnus-function-implies-unread-1(#[nil "À ?" [gnus-agent-read-p] 1])
>   gnus-predicate-implies-unread((not read))
>   gnus-agent-fetch-headers("nntp+gmane:gmane.comp.db.dbworld")
>   gnus-agent-fetch-group-1("nntp+gmane:gmane.comp.db.dbworld" (nntp "gmane" (nntp-address "news.gmane.org")))
>   gnus-agent-fetch-session()
>   call-interactively(gnus-agent-fetch-session)
>
> I applied the following patch to make it go away.  I am, however,
> quite unsure if this was the right thing to do.
>
> Does anyone know what's the right thing to do?
>
> Index: lisp/gnus-agent.el
> ===================================================================
> RCS file: /usr/local/cvsroot/gnus/lisp/gnus-agent.el,v
> retrieving revision 6.151
> diff -u -r6.151 gnus-agent.el
> --- lisp/gnus-agent.el	4 Mar 2003 01:43:59 -0000	6.151
> +++ lisp/gnus-agent.el	4 Mar 2003 10:55:59 -0000
> @@ -2344,7 +2344,7 @@
>           nil)
>          ((not function)
>           nil)
> -        ((symbolp function)
> +        ((gnus-functionp function)
>           'ignore)
>          ((memq (car function) '(or and not))
>           (apply (car function)
>

We may need both to handle code being interpreted versus compiled.  I
going to be off-line all day, if you have something that works, please
check it in.

Thanks,
Kevin



  reply	other threads:[~2003-03-04 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 10:37 Kai Großjohann
2003-03-04 13:11 ` Kevin Greiner [this message]
2003-03-04 13:31   ` Kai Großjohann

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=uznob8eeq.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).