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: Wed, 12 Oct 2022 00:26:12 +0200 Message-ID: <87a6620zgb.fsf@dataswamp.org> References: <83k05pjov1.fsf@gnu.org> <875yh96r2n.fsf@web.de> <87bkqs1i2r.fsf@dataswamp.org> <87zge3z2i7.fsf@dataswamp.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="27124"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:WMisLPTKHYJDfT7McRocscLs1Qg= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Oct 12 11:17:08 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 1oiXrQ-0006nm-9Q for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 12 Oct 2022 11:17:08 +0200 Original-Received: from localhost ([::1]:42468 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oiXrP-00053Z-04 for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 12 Oct 2022 05:17:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50714) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oiNhg-0004SR-Hq for help-gnu-emacs@gnu.org; Tue, 11 Oct 2022 18:26:24 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:34374) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oiNhe-0007xq-JV for help-gnu-emacs@gnu.org; Tue, 11 Oct 2022 18:26:24 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oiNhb-00013u-SX for help-gnu-emacs@gnu.org; Wed, 12 Oct 2022 00:26:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org 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, 12 Oct 2022 05:12:38 -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:139847 Archived-At: Jean Louis wrote: >>>>>> Try `M-x check-parens RET` >>>>> >>>>> That is good, thank you. >>>> >>>> But nothing ever happens with that? >>> >>> Since then I have used it, it finds the place where >>> parenthesis is missing. >> >> Ah, I see now, you have to remove a paren (break the code) >> for it to "work" :) > > check-parens finds the missing parenthesis, so it is other > way around. It can't, and it isn't :) >>> It should also be involved in those error messages >> >> Yes, sounds reasonable, I wonder tho if you can get "out >> parsed" only by parenthesis mismatch or if there are other >> ways to do that? >> >>> to at least estimate >> >> Estimate, that's how it works? > > When there is compiling process, then such fails without > giving enough information. Instead of failing, process could > use functions in check-parens to indicate where could be the > problem in the code, and provide link for user to click on > the link and quickly invoke check-parens > > I did not know that function exist. It is not enough > integrated in Emacs. Do it yourself, Jean :) -- underground experts united https://dataswamp.org/~incal