Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: End of file during parsing, single newsgroup
Date: Fri, 28 Sep 2012 11:38:34 +0200	[thread overview]
Message-ID: <87bogqwkpx.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87mx0abjx0.fsf@gmail.com>

William Gardella <gardellawg@gmail.com>
writes:

>>> Before trying to enter that group, do M-x toggle-debug-on-error RET
>>> and post the backtrace here.
>>
>> This is what I got:
>>
>> Debug on Error enabled globally
>> Retrieving newsgroup: rec.arts.sf.written...
>> Fetching headers for rec.arts.sf.written...
>> byte-code: End of file during parsing
>> Commands: d, s, x, u; f, o, 1, 2, m, v; ~, %; q to quit; ? for help.
>>
>> At the moment it looks like no clear message from the debugger,or it
>> is not entering it given the Commands line.

Strange.  What does it say when you hit `?'?

> Could the "end of file during parsing" be corruption in the
> ~/.newsrc.eld file?  That's my only (possibly pretty far-fetched)
> guess.

I think, if it was corrupted it would error as soon as gnus tries to
read it the first time and not only with this one specific group.

Some more guesses:

  - Do you have (gnus-compile) in your ~/.gnus.el?  If so, comment it
    out and restart emacs.  Fire up Gnus, do something and hit `s' in
    *Group* so that it saves the ~/.newsrc.eld.  Restart emacs and gnus
    and try to enter rec.arts.sf.written.  I think, you still get an
    error but maybe a bit more informative.

  - Do you have a special gnus-summary-line-format set for that group,
    e.g., via gnus-parameters?  Maybe that's somehow broken?

  - 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.

Bye,
Tassilo

  reply	other threads:[~2012-09-28  9:38 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 [this message]
     [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

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=87bogqwkpx.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --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).