From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: Error: End of file during parsing Date: Tue, 27 Sep 2022 15:28:03 +0200 Message-ID: <87v8p96j6k.fsf@dataswamp.org> References: <87wn9pqqfl.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22778"; 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:4ho2KCgftKpu1PlFkJFsjZv5Vb8= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 28 14:03:05 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 1odVmL-0005h4-8v for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 28 Sep 2022 14:03:05 +0200 Original-Received: from localhost ([::1]:49868 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odVmJ-0004TE-Pm for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 28 Sep 2022 08:03:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54558) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odAdD-0006AH-Eh for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 09:28:15 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:54868) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odAdA-0006Z6-Eg for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 09:28:15 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1odAd8-00044x-FF for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 15:28:10 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org In-Reply-To: <87wn9pqqfl.fsf@dataswamp.org> (Emanuel Berg's message of "Tue, 27 Sep 2022 08:31:10 +0200") Mail-Copies-To: never 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: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, 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-Mailman-Approved-At: Wed, 28 Sep 2022 05:46:52 -0400 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:139658 Archived-At: Jean Louis wrote: >> If there is end of file during parsing, then why Emacs >> cannot tell me at what line number it encountered error? And the answer is even more specific: at the end of the last line. Maybe also it should say unbalanced parens? But actually it can also be e.g. a string that isn't closed. E.g., EOF during file persing (do you have unbalanced parens?) Well, that would be the most likely in Lisp at least ... But cannot this be fixed mechanically by just adding closing parens (or the corresponding close char) until it's OK? Yes, the balancing problem can, but it may still be incorrect Elisp, e.g (( (err msg "Containing expression ends prematurely") damn -> (()) (Symbol’s function definition is void: nil rats -- underground experts united https://dataswamp.org/~incal