From: Stephen Harker <sjharker@netspace.net.au>
To: info-gnus-english@gnu.org
Subject: Re: End of file during parsing, single newsgroup
Date: Sun, 30 Sep 2012 08:06:02 +1000 [thread overview]
Message-ID: <m3a9w8scvp.fsf@howitt.home> (raw)
In-Reply-To: <m3txuizaif.fsf@howitt.home>
Stephen Harker <sjharker@netspace.net.au> writes:
> Tassilo Horn <tsdh@gnu.org> writes:
>
>> William Gardella <gardellawg@gmail.com>
>> writes:
>> - Did you use a newer version of emacs once? If so, maybe the
>> (gnus-compile) compiled something in ~/.newsrc.eld to byte-code
>> that's not understood by emacs 22.
>
> That is a possibility. I started an install of Fedora 17 and don't
> think I did anything in the home partition, but can't guaranteee
> it.
This led to a solution. I used Fedora 17 which comes with emacs 24, I
think it was emacs-24.1-4. Running gnus with the later emacs and
opening rec.arts.sf.written resulted in an error message saying there
was a fault in the rec.arts.sf.written.ADAPT file, but proceeding and
overwriting it after exiting with a version that works with the older
emacs also.
When I replaced the rec.arts.sf.written.ADAPT with a backup version I
must not have gone far enough back. It may have been the first
version in which the error was written to the file. I thought I had
gone back two days, but evidently not.
--
Stephen Harker s.harker@adfa.edu.au
PEMS http://sjharker.customer.netspace.net.au/
UNSW@ADFA
prev parent reply other threads:[~2012-09-29 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 9:05 Stephen Harker
2012-09-27 11:24 ` Tassilo Horn
[not found] ` <mailman.9845.1348745114.855.info-gnus-english@gnu.org>
2012-09-28 8:01 ` Stephen Harker
2012-09-28 9:01 ` William Gardella
2012-09-28 9:38 ` Tassilo Horn
[not found] ` <mailman.9918.1348825141.855.info-gnus-english@gnu.org>
2012-09-28 10:50 ` Stephen Harker
2012-09-29 22:06 ` Stephen Harker [this message]
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=m3a9w8scvp.fsf@howitt.home \
--to=sjharker@netspace.net.au \
--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).