From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Trouble with nnir.el ("Invalid function ...")
Date: Tue, 29 Jul 2003 16:13:54 +0200 [thread overview]
Message-ID: <84k7a1xvx9.fsf@slowfox.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <87adaxbozu.fsf@phiwumbda.localnet>
jesseh@cs.kun.nl (Jesse F. Hughes) writes:
>> | Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>> | aset(nil 0 1)
>> | (mail-header-set-number novitem idx)
>> | (while (not (null artlist)) (setq art (car artlist)) (or (numberp art) (nnheader-report ... "nnir-retrieve-headers doesn't grok message ids: %s" art)) (setq artitem (nnir-artlist-article nnir-artlist art)) (setq artrsv (nnir-artitem-rsv artitem)) (setq artfullgroup (nnir-artitem-group artitem)) (setq artno (nnir-artitem-number artitem)) (setq artgroup (gnus-group-real-name artfullgroup)) (setq server (nnir-group-server artfullgroup)) (set-buffer nntp-server-buffer) (nnir-possibly-change-server server) (case (setq foo ...) (nov ... ... ...) (headers ... ... ...) (t ...)) (mail-header-set-number novitem idx) (mail-header-set-from novitem (mail-header-from novitem)) (mail-header-set-subject novitem (format "[%d: %s/%d] %s" artrsv artgroup artno ...)) (push novitem novdata) (setq artlist (cdr artlist)) (setq idx (1+ idx)))
Really strange. Have a look at this code:
(nnir-possibly-change-server server)
(case (setq foo (gnus-retrieve-headers (list artno) artfullgroup nil))
(nov
(goto-char (point-min))
(setq novitem (nnheader-parse-nov))
(unless novitem
(pop-to-buffer nntp-server-buffer)
(error
"nnheader-parse-nov returned nil for article %s in group %s"
artno artfullgroup)))
(headers
(goto-char (point-min))
(setq novitem (nnheader-parse-head))
(unless novitem
(pop-to-buffer nntp-server-buffer)
(error
"nnheader-parse-head returned nil for article %s in group %s"
artno artfullgroup)))
(t (nnheader-report 'nnir "Don't support header type %s." foo)))
;; replace article number in original group with article number
;; in nnir group
(mail-header-set-number novitem idx)
I think the error is coming from there. Now, the case statement
calls gnus-retrieve-headers and then looks at the result. If the
result is nov, novitem is set and then checked for non-nil-ness. If
the result is headers, then also novitem is set and then checked for
non-nil-ness. And if the result was neither nov nor headers, then an
error is generated.
Thus, I expect that the last line from the above snippet is never
reached for novitem being nil.
What's wrong in this reasoning?
Could you position point inside that function and do M-x edebug-defun
RET and then use SPC to single-step through it to see what's happening?
--
~/.signature
next prev parent reply other threads:[~2003-07-29 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xeq3smp0dxpx.fsf@desh.cisco.com>
[not found] ` <84znj7q8u0.fsf@lucy.is.informatik.uni-duisburg.de>
2003-07-23 7:34 ` Sriram Karra
[not found] ` <87adaxbozu.fsf@phiwumbda.localnet>
2003-07-29 14:13 ` Kai Großjohann [this message]
[not found] ` <87y8yh5hbb.fsf@phiwumbda.localnet>
[not found] ` <84zniw59nn.fsf@slowfox.is.informatik.uni-duisburg.de>
2003-07-30 17:28 ` Sriram Karra
[not found] ` <84he51mfp3.fsf@slowfox.is.informatik.uni-duisburg.de>
[not found] ` <xeq3vft1eke4.fsf@desh.cisco.com>
2003-08-13 20:21 ` Jesse F. Hughes
2003-07-30 17:29 ` Jesse F. Hughes
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=84k7a1xvx9.fsf@slowfox.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).