From: Laura Conrad <lconrad@laymusic.org>
Subject: Error getting into gnus
Date: Mon, 20 Aug 2001 09:46:09 -0400 (EDT) [thread overview]
Message-ID: <20010820134609.459C51FD8E@serpent> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Trying to get into gnus (I think Saturday afternoon CVS), I get the
following backtrace:
Signaling: (wrong-type-argument stringp nil)
intern-soft(nil [0 nntp+news\.speakeasy\.net:rec\.music\.early nnml+private:websurf nnml+private:linart 0 0 nnml+private:sunny 0 0 nnml+private:pilot-unix 0 0 0 0 0 0 0 0 0 nnml+private:abcdiscuss comp\.lang\.python 0 nntp+news-east\.speakeasy\.net:rec\.humor\.funny nntp+news\.speakeasy\.net:rec\.humor\.funny nnml+private:wwwacct alt\.binaries\.vcd 0 0 0 0 0 0 0 0 nnml+private:world\.old 0 0 comp\.sys\.palmtops\.pilot 0 0 0 0 0 0 0 0 0 0 0 nnml+private:woyp])
gnus-group-highlight-line()
run-hooks(gnus-group-update-hook)
apply(run-hooks gnus-group-update-hook)
gnus-run-hooks(gnus-group-update-hook)
gnus-group-insert-group-line("dummy.group" 0 nil 0 nil)
gnus-update-group-mark-positions()
gnus-group-mode()
gnus-group-setup-buffer()
gnus-group-list-groups(nil)
byte-code("\b„\x0e
gnus-1(nil nil nil)
gnus()
command-line-1(("-f" "gnus"))
command-line()
normal-top-level()
It's still happening with the most recent cvs, and also happens with
ognus 0.3, so it must be something having clobbered my files.
Any suggestions for getting them back?
next reply other threads:[~2001-08-20 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 13:46 Laura Conrad [this message]
2001-08-21 21:53 ` Lars Magne Ingebrigtsen
2001-08-21 23:21 ` Laura Conrad
2001-08-23 18:02 ` Lars Magne Ingebrigtsen
2001-08-24 13:11 ` Laura Conrad
2001-08-24 14:05 ` 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=20010820134609.459C51FD8E@serpent \
--to=lconrad@laymusic.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).