Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@void.at>
Subject: Re: "End of file during parsing" in Gcc handling
Date: Thu, 10 Oct 2002 21:35:07 +0200	[thread overview]
Message-ID: <E17zj5P-0008Ap-00@eris.void.at> (raw)
In-Reply-To: <m3adlm2knz.fsf@multivac.cwru.edu>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

Today, Paul Jarc <prj@po.cwru.edu> wrote:
>> Now, stepping through `gnus-inews-do-gcc', shows me that the error
>> happens somewhere inside or after a call to
>> `gnus-request-accept-article'. When I instrument this defun and step
>> through it, nothing happens until after emacs jumps out of it, when I
>> get this error: "End of file during parsing" (But no backtrace,
>> grrrr.)
> 
> Random guess: do you use any advice for that function?

Seems not to be so.

,----[ `gnus-request-accept-article' function documentation ]
| gnus-request-accept-article is a Lisp function in `gnus-int'.
| (gnus-request-accept-article GROUP &optional GNUS-COMMAND-METHOD LAST NO-ENCODE)
| 
| Not documented.
`----

Obviously not. Maybe my draft groups are broken? Can I regenerate their
active files or overview database without causing harm?

Thanks,
-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
Was I helpful?  Let others know:
http://svcs.affero.net/rm.php?r=antifuchs

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2002-10-10 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 11:43 Andreas Fuchs
2002-10-10 15:03 ` Simon Josefsson
2002-10-10 18:40   ` Andreas Fuchs
2002-10-10 20:23     ` Simon Josefsson
2002-10-10 20:58       ` Andreas Fuchs
2002-10-11  8:33         ` Kai Großjohann
2002-10-11 17:35           ` Andreas Fuchs
2002-10-11 17:38           ` Andreas Fuchs
2002-10-10 18:49 ` Paul Jarc
2002-10-10 19:35   ` Andreas Fuchs [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=E17zj5P-0008Ap-00@eris.void.at \
    --to=asf@void.at \
    /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).