From: Gregory Heytings <gregory@heytings.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Error: End of file during parsing
Date: Tue, 27 Sep 2022 11:48:25 +0000 [thread overview]
Message-ID: <94a8e877a7e62d9e6568@heytings.org> (raw)
In-Reply-To: <875yh96r2n.fsf@web.de>
>> 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.
>
> If a file contains N open parens and N+1 closing parens, or the other
> way round, Emacs can't even know or conclude what the programmer
> actually wanted to write. This kind of problem requires some manual
> error searching by the programmer.
>
If a file contains N open parens and N+1 closing parens, Emacs displays an
error message pointing to the closing paren to which no opening paren
corresponds.
If a file contains N+1 open parens and N closing parens, Emacs displays an
"End of file during parsing" error message. It could be a bit smarter,
though: if one assumes that the file is properly indented, which is
usually the case, whenever a parenthesis is read in column 1, the number
of opening and closing parens must match. IOW, Emacs could point to the
first such place where this is not the case. Such a hint would not be
100% accurate, but would be helpful.
next prev parent reply other threads:[~2022-09-27 11:48 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
2022-09-27 10:37 ` Michael Heerdegen
2022-09-27 11:48 ` Gregory Heytings [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94a8e877a7e62d9e6568@heytings.org \
--to=gregory@heytings.org \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.