unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Error: End of file during parsing
Date: Tue, 27 Sep 2022 09:46:58 +0300	[thread overview]
Message-ID: <83k05pjov1.fsf@gnu.org> (raw)
In-Reply-To: <courier.0000000063329666.00002741@stw1.rcdrun.com> (message from Jean Louis on Tue, 27 Sep 2022 09:20:34 +0300)

> Date: Tue, 27 Sep 2022 09:20:34 +0300
> From: Jean Louis <bugs@gnu.support>
> 
> This condition is terrible:
> 
> Compiling file /home/data1/protected/Programming/emacs-lisp/rcd-cf.el at Tue Sep 27 09:18:19 2022
> rcd-cf.el: Error: End of file during parsing
> 
> If there is end of file during parsing, then why Emacs cannot tell me
> at what line number it encountered error?

It did tell you: the error is at EOF.  That's where Emacs realized
that there is an error.  It cannot do that earlier.

The problem is likely unbalanced parentheses somewhere.



  parent reply	other threads:[~2022-09-27  6:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  6:20 Error: End of file during parsing Jean Louis
2022-09-27  6:31 ` Emanuel Berg
2022-09-27 13:28   ` Emanuel Berg
2022-09-27  6:46 ` Eli Zaretskii [this message]
2022-09-27 10:37   ` Michael Heerdegen
2022-09-27 11:48     ` Gregory Heytings
2022-09-27 15:06       ` Michael Heerdegen
2022-09-27 11:50     ` Jean Louis
2022-09-27 15:44       ` Michael Heerdegen
2022-09-28 11:42       ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-03 23:35         ` Jean Louis
2022-10-04  1:41           ` Emanuel Berg
2022-10-10  6:08             ` Jean Louis
2022-10-10 23:24               ` Emanuel Berg
2022-10-11 19:00                 ` Jean Louis
2022-10-11 22:26                   ` Emanuel Berg
2022-10-12 13:14                     ` Jean Louis
2022-10-12 20:02                       ` Emanuel Berg
2022-10-15 14:28                         ` Alessandro Bertulli
2022-09-28  6:24 ` Christopher M. Miles

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k05pjov1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).