From: Eze Ogwuma <typhoon@dircon.co.uk>
Cc: ding@gnus.org
Subject: Re: Bad .newsrc.eld created by Gnus
Date: 08 Feb 1998 21:31:00 +0000 [thread overview]
Message-ID: <m3u3a9rdgr.fsf@localhost.localdomain> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "08 Feb 1998 21:00:47 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Eze Ogwuma <typhoon@dircon.co.uk> writes:
>
> > > > > What does the end of the .eld file look like?
> > > >
> > > > (version . "20.2.1")))
> > >
> > > What are the last two or three lines?
> >
> > This follows the topic a-list:
>
> Yes -- but that format spec looks ok to me.
>
> Try putting the .newsrc.eld file into a buffer and type
> `M-x eval-current-buffer RET' to see where the problem is.
I get the error:
Signaling: (invalid-read-syntax "#")
eval-buffer(#<buffer ".newsrc-localhost.eld"> nil)
#<compiled-function (from "simple.elc") (&optional printflag) "...(5)" [eval-buffer printflag] 3 673955 nil>()
call-interactively(eval-current-buffer)
command-execute(eval-current-buffer t)
execute-extended-command(nil)
call-interactively(execute-extended-command)
This is part of my file. It is the only part that contains "#".
(#("nntp+news.dircon.co.uk:comp.lang.java.help" 0 23 nil 23 42
(mouse-face highlight face gnus-group-news-3-face)) 3 ((1 . 13981)
13983 (13985 . 13991) (13997 . 14004) 14006 (14009 . 14010) 14012
(14015 . 14018) (14021 . 14025) (14027 . 14029) (14031 . 14032) (14035
. 14038) (14041 . 14044) (14050 . 14051) 14055 14060 14062 14064 14068
14080 14083 (14085 . 14087) (14090 . 14092) (14097 . 14099) (14101
. 14102) 14106 14109 (14111 . 14112) 14114 14119 (14121 . 14122) 14124
14129 14131 (14133 . 14137) (14139 . 14149) (14156 . 14157) 14159
14161 (14163 . 14166) (14169 . 14170) (14174 . 14179) 14183 14186
14189 14192 14194 (14197 . 14198) (14205 . 14207) 14209 14215 14217
(14219 . 14220) (14228 . 14229) 14234 (14236 . 14237) (14241 . 14243)
(14246 . 14249) (14253 . 14254) (14257 . 14258) 14316 14417 14444
14479 (14525 . 14526) 14546) ((cache 12238 13613 13728 13783 13836
13859 13887 14051 14526) (tick 13613 13728 13783)) (nntp
"news.dircon.co.uk"))
(#("nntp+news.dircon.co.uk:comp.lang.java.programmer" 0 23 nil 23 48
(mouse-face highlight face gnus-group-news-3-face)) 3 ((1 . 105594)
105612 105781 106073 106076 106087 106122 106182 106232 106911) nil
--
Eze Ogwuma
next prev parent reply other threads:[~1998-02-08 21:31 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 [this message]
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
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=m3u3a9rdgr.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).