From: Benjamin Slade <slade@jnanam.net>
To: info-gnus-english <info-gnus-english@gnu.org>
Subject: complete crash of gnus - (wrong-type-argument number-or-marker-p nil)
Date: Wed, 7 Sep 2016 23:03:36 -0600 [thread overview]
Message-ID: <CAH+j8rDfd2HaRruOVtT4+hqZVyVSEYRu+HKTtsGop8ae6ufq7A@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2162 bytes --]
Somehow my groups screen in Gnus got completely buggered up today. Then I
exited Gnus and tried to re-entered and I get an error:
(wrong-type-argument number-or-marker-p nil)
gnus-group-change-level(nil nil nil nil t)
eval-buffer(#<buffer .newsrc-dribble>) ; Reading at buffer position
117784
gnus-dribble-eval-file()
gnus-setup-news(nil nil nil)
byte-code(" \204 \204 \306 \210\202L\307\310!\210\311\n! \f\204
\203!\312 \210\313\314 #\210\307\315!\210 \2036\316\317\320\"\210\321
\210\322 !\210\323 \210\324\325!\210\326 \210\307\327!\210\314\207"
[dont-connect did-connect gnus-startup-file gnus-current-startup-file
gnus-slave gnus-use-dribble-file gnus-group-quit gnus-run-hooks
gnus-startup-hook gnus-make-newsrc-file gnus-dribble-read-file
gnus-setup-news nil gnus-setup-news-hook gnus-request-create-group "queue"
(nndraft "") gnus-start-draft-setup gnus-group-list-groups
gnus-group-first-unread-group gnus-configure-windows group
gnus-group-set-mode-line gnus-started-hook level gnus-agent] 4)
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus nil nil)
command-execute(gnus)
[ stepping through, I get:
Debugger entered--entering a function:
* command-error-default-function((wrong-type-argument number-or-marker-p
nil) "" byte-code)
Debugger entered--entering a function:
* sml/-this-buffer-changed(1 2 0)
* command-error-default-function((wrong-type-argument number-or-marker-p
nil) "" byte-code)
and so on....]
I've tried restoring from a backup the .newsrc and .newsrc.eld files
What I would really like is just to get back a working gnus. What is the
best way of just resetting at this point?
-----------------------------------------------------------------------------------------------------
"While corporations dominate society and write the laws,
each advance in technology is an opening for them
to further restrict its users."
--Stallman's Law
-----------------------------------------------------------------------------------------------------
* {Choose freedom: choose GNU <http://www.gnu.org> & Linux
<http://www.whylinuxisbetter.net>.}*
[-- Attachment #1.2: Type: text/html, Size: 3220 bytes --]
next reply other threads:[~2016-09-08 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 5:03 Benjamin Slade [this message]
2016-09-08 17:17 ` Arkady Grudzinsky
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=CAH+j8rDfd2HaRruOVtT4+hqZVyVSEYRu+HKTtsGop8ae6ufq7A@mail.gmail.com \
--to=slade@jnanam.net \
--cc=info-gnus-english@gnu.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).