From: Jorge Godoy <godoy@ieee.org>
Subject: How can I fix that problem? (A different debug included)
Date: Thu, 18 Dec 2003 15:46:49 -0200 [thread overview]
Message-ID: <m31xr281di.fsf@ieee.org> (raw)
Hi, sorry for reposting this. This debug message is different from the
previous one and might give another hint on the problem.
I'm trying to access a group after a crash here (due to power failure)
and I keep getting an error of '(wrong-type-argument sequencep
s)'. Anybody can help me fix that? I've tried unsubscribing, deleting,
killing, etc. this group but nothing worked.
If I delete de '.ADAPT' file for it I can get in the group but then
when I try reentering it I get the error message again.
If it is needed I can attach the 'comp.lang.python.ADAPT' file to a
message in private or to the list.
Here's the debug:
Debugger entered--Lisp error: (wrong-type-argument sequencep s)
gnus-score-string((((touched t) ("subject" ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) ("from" ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...))) "from" 731567 731560 nil)
gnus-score-headers(("/home/godoy/News/comp.lang.python.ADAPT" "/home/godoy/News/comp.lang.python.SCORE") nil)
gnus-possibly-score-headers()
gnus-summary-read-group-1("comp.lang.python" nil nil nil nil nil)
gnus-summary-read-group("comp.lang.python" nil nil nil nil nil nil)
gnus-group-read-group(nil nil nil)
gnus-topic-read-group(nil)
call-interactively(gnus-topic-read-group)
recursive-edit()
byte-code("Æ\b!ˆÇ ˆÈ !ˆ\nƒ?\0Éed\"\vVƒ4\0ebˆÊ\v¥yˆ`\x1cdbˆÊ\v¥\vZyˆ\f`|ˆ)ËcˆebˆÌÍ !ˆÎ ˆ @Ï=ƒK\0ÐÑÒ\"ˆÓ ˆÌÔ!ˆÒÕÒ\x1d\x1e\x17\x1e\x18ÌÔ!ˆŠÖ ˆ,Õ‡" [debugger-buffer debugger-args noninteractive debugger-batch-max-lines middlestart buffer-read-only pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output inhibit-trace] 3)
debug(error (wrong-type-argument sequencep s))
gnus-score-string((((touched t) ("subject" ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) ("from" ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...))) "from" 731567 731560 nil)
gnus-score-headers(("/home/godoy/News/comp.lang.python.ADAPT" "/home/godoy/News/comp.lang.python.SCORE") nil)
gnus-possibly-score-headers()
gnus-summary-read-group-1("comp.lang.python" nil t nil nil nil)
gnus-summary-read-group("comp.lang.python" nil t nil nil nil nil)
gnus-group-read-group(nil t)
gnus-group-select-group(nil)
gnus-topic-select-group(nil)
call-interactively(gnus-topic-select-group)
next reply other threads:[~2003-12-18 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 17:46 Jorge Godoy [this message]
2003-12-22 11:20 ` Yair Friedman
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=m31xr281di.fsf@ieee.org \
--to=godoy@ieee.org \
/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).