From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Error: End of file during parsing
Date: Tue, 27 Sep 2022 17:06:46 +0200 [thread overview]
Message-ID: <87zgek6em1.fsf@web.de> (raw)
In-Reply-To: 94a8e877a7e62d9e6568@heytings.org
Gregory Heytings <gregory@heytings.org> writes:
> 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.
Would be helpful, yes. I'm not sure about the usually intact
indentation, though: sometimes when that happened to me indentation of
other top-level expressions had been messed up. Can happen very quickly
once such an accident occurred.
Anyway - does that mean you think the compiler should do this?
Michael.
next prev parent reply other threads:[~2022-09-27 15:06 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
2022-09-27 15:06 ` Michael Heerdegen [this message]
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=87zgek6em1.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).