From: Eze Ogwuma <typhoon@dircon.co.uk>
Cc: ding@gnus.org
Subject: Re: Bad .newsrc.eld created by Gnus
Date: 09 Feb 1998 01:49:34 +0000 [thread overview]
Message-ID: <m37m75tump.fsf@localhost.localdomain> (raw)
In-Reply-To: SL Baur's message of 08 Feb 1998 17:28:00 -0800
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
SL Baur <steve@xemacs.org> writes:
> Eze Ogwuma <typhoon@dircon.co.uk> writes:
>
> > SL Baur <steve@xemacs.org> writes:
>
> >> Who put in the #'s? That's not valid Emacs or XEmacs.
>
> > Not me. I didn't think they should be there. Perhaps the file was
> > corrupted when X crashed a while back.
>
> The first snippet didn't look corrupted. The parens were balanced.
I tried taking out the "#" marks while leaving the parens intact but I
got this error:
Signaling: (wrong-type-argument stringp ("nntp+news.dircon.co.uk:comp.lang.java.help" 0 23 nil 23 42 (mouse-face highlight face gnus-group-news-3-face)))
intern(("nntp+news.dircon.co.uk:comp.lang.java.help" 0 23 nil 23 42 (mouse-face highlight face gnus-group-news-3-face)) [comp\.os\.linux\.setup 0 0 comp\.os\.linux\.development\.apps 0 comp\.os\.linux\.hardware 0 0 0 0 0 0 0 0 0 0 0 nnml:redhat\.digests\.v97\.p1 nnml:redhat\.digests\.v97\.p2 nnml:redhat\.digests\.v96\.p3 0 gnu\.announce 0 0 0 0 0 0 0 0 0 0 0 0 0 comp\.emacs\.xemacs 0 nnml:hurricane 0 nnml:sag nnml:inbox 0 0 0 null 0 0 0 0 0 ...])
gnus-make-hashtable-from-newsrc-alist()
gnus-read-newsrc-el-file("/home/zcaceog/.newsrc-localhost.el")
gnus-read-newsrc-file(nil)
gnus-setup-news(nil nil nil)
byte-code("\b¬ ¬
 ª»ÃÄ!Å\x0e\x06!\x16\a\x0e\b¬\x0e «Ê \x0e\v«Ì ÍÎÏ\"ÐÑ\x0e\x12\b#Ó\x0e\x12!Ô ÕÖ!× ÃØ!Ñ" [dont-connect did-connect gnus-group-quit run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-dribble-read-file gnus-use-grouplens bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil level gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook] 4)
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus)
command-execute(gnus t)
execute-extended-command(nil)
call-interactively(execute-extended-command)
--
Eze Ogwuma
next prev parent reply other threads:[~1998-02-09 1:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-03 18:37 Eze Ogwuma
1998-02-04 15:15 ` Simon Josefsson
1998-02-04 17:42 ` Eze Ogwuma
1998-02-04 19:13 ` Bud Rogers
1998-02-04 19:22 ` Eze Ogwuma
1998-02-04 17:54 ` Eze Ogwuma
1998-02-04 18:35 ` David S. Goldberg
1998-02-04 19:25 ` Eze Ogwuma
1998-02-04 19:01 ` Simon Josefsson
1998-02-04 19:44 ` Eze Ogwuma
1998-02-08 15:57 ` Lars Magne Ingebrigtsen
1998-02-08 16:59 ` Eze Ogwuma
1998-02-08 17:23 ` Lars Magne Ingebrigtsen
1998-02-08 19:17 ` Eze Ogwuma
1998-02-08 20:00 ` Lars Magne Ingebrigtsen
1998-02-08 21:31 ` Eze Ogwuma
1998-02-09 0:29 ` SL Baur
1998-02-09 0:50 ` Eze Ogwuma
1998-02-09 1:28 ` SL Baur
1998-02-09 1:49 ` Eze Ogwuma [this message]
1998-02-09 2:02 ` SL Baur
1998-02-09 2:47 ` Eze Ogwuma
1998-02-09 8:18 ` Hrvoje Niksic
1998-02-09 9:47 ` Per Abrahamsen
[not found] ` <6fk9b5kssq.fsf@bavur.dna.lth.se>
1998-02-09 18:57 ` Eze Ogwuma
1998-02-09 20:10 ` Lars Magne Ingebrigtsen
1998-02-09 20:56 ` Eze Ogwuma
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=m37m75tump.fsf@localhost.localdomain \
--to=typhoon@dircon.co.uk \
--cc=ding@gnus.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).