From: Torsten Hilbrich <gnus@myrkr.in-berlin.de>
Subject: gnus-string-equal broken by using compare-strings
Date: Thu, 17 Apr 2003 08:29:31 +0200 [thread overview]
Message-ID: <87r8811vsk.fsf@myrkr.in-berlin.de> (raw)
Hello
I just update gnus from CVS and got the following error when
displaying any article:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
compare-strings(nil nil nil "local.debian.user-german" nil nil t)
gnus-string-equal(nil "local.debian.user-german")
article-hide-boring-headers()
apply(article-hide-boring-headers nil)
(if interactive (call-interactively (quote article-hide-boring-headers)) (apply (quote article-hide-boring-headers) args))
(save-excursion (set-buffer gnus-article-buffer) (if interactive (call-interactively ...) (apply ... args)))
gnus-article-hide-boring-headers()
gnus-treat-article(head)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(46120 nil)
gnus-summary-display-article(46120 nil)
gnus-summary-select-article(nil nil pseudo)
gnus-summary-scroll-up(1)
call-interactively(gnus-summary-scroll-up)
I debugged a little bit and found out that the error happens here:
Function: article-hide-boring-headers, line 1664:
((eq elem 'followup-to)
(when (gnus-string-equal
(message-fetch-field "followup-to")
(message-fetch-field "newsgroups"))
(gnus-article-hide-header "followup-to")))
(message-fetch-field "followup-to") returns nil and gnus-string-equal
bails out because it is defined as:
(defun gnus-string-equal (x y)
"Like `string-equal', except it compares case-insensitively."
(eq t (compare-strings x nil nil y nil nil t)))
compare-strings doesn't like its x/y arguments to be nil.
I checked against the older version and there the compare-string
function is not used at all, so the problem seems to be this change.
Torsten
next reply other threads:[~2003-04-17 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 6:29 Torsten Hilbrich [this message]
2003-04-27 3:02 ` Lars Magne Ingebrigtsen
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=87r8811vsk.fsf@myrkr.in-berlin.de \
--to=gnus@myrkr.in-berlin.de \
/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).