From: Michel Schinz <schinz@studi.epfl.ch>
Subject: Problem at startup: wrong-type-argument listp __uninitialized__
Date: 19 Jun 1996 11:29:56 +0200 [thread overview]
Message-ID: <oet3f3sjg4r.fsf@studi.epfl.ch> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hi there!
My workstation crashed badly the other day, and now I have a new
problem with Gnus, but I don't know whether this is a bug or not.
Here is what happens: when I launch Gnus, I get the following error
message:
wrong-type-argument listp __uninitialized__
Here is what I get with debug-on-error set to true:
Signalling: (wrong-type-argument listp __uninitialized__)
gnus-group-highlight-line()
run-hooks(gnus-group-update-hook)
gnus-group-insert-group-line("dummy.group" 0 nil 0 nil)
gnus-update-group-mark-positions()
gnus-update-format-specifications()
gnus-setup-news(nil nil nil)
byte-code("\b„\x0e
gnus(nil)
call-interactively(gnus)
execute-extended-command(nil)
call-interactively(execute-extended-command)
I tried to take a look at the gnus-group-highlight-line function and I
found that the problem is that the gnus-group-highlight variable is
set to __uninitialized__. But I wasn't able to go further and find
why it was set to this value.
The only workaround that I have found is to set gnus-visual to nil so
that gnus-group-highlight-line isn't called, but now I really miss the
visual features of Gnus. Could someone help me and tell me how I
could correct that? Thanks.
OBTW, I'm using Gnus 5.2.20.
Michel.
reply other threads:[~1996-06-19 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=oet3f3sjg4r.fsf@studi.epfl.ch \
--to=schinz@studi.epfl.ch \
/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).