From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.help Subject: Re: Error: End of file during parsing Date: Tue, 27 Sep 2022 17:06:46 +0200 Message-ID: <87zgek6em1.fsf@web.de> References: <83k05pjov1.fsf@gnu.org> <875yh96r2n.fsf@web.de> <94a8e877a7e62d9e6568@heytings.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23733"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:K4li084NWjKxOIUw2bQECBD59Pg= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Sep 27 17:41:35 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1odCiE-0005z0-Pl for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 27 Sep 2022 17:41:34 +0200 Original-Received: from localhost ([::1]:42460 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odCiD-00056L-II for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 27 Sep 2022 11:41:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37992) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odCAp-0001hw-Nr for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 11:07:07 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:33696) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odCAj-0008UU-74 for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 11:07:02 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1odCAg-0009rY-Oc for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 17:06:54 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:139648 Archived-At: Gregory Heytings 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.