From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: Error: End of file during parsing Date: Tue, 27 Sep 2022 14:50:07 +0300 Message-ID: References: <83k05pjov1.fsf@gnu.org> <875yh96r2n.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1366"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ () (2022-06-11) Cc: help-gnu-emacs@gnu.org To: Michael Heerdegen Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Sep 27 17:52:32 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 1odCsq-00009d-UG for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 27 Sep 2022 17:52:32 +0200 Original-Received: from localhost ([::1]:38186 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odCsp-0007w8-EG for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 27 Sep 2022 11:52:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54838) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odABZ-0004d8-75 for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 08:59:42 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:34687) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odABX-0000Yr-1N for help-gnu-emacs@gnu.org; Tue, 27 Sep 2022 08:59:40 -0400 Original-Received: from localhost ([::ffff:197.239.4.116]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 00000000000BA40A.000000006332F395.00006FF3; Tue, 27 Sep 2022 05:59:01 -0700 Mail-Followup-To: Michael Heerdegen , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <875yh96r2n.fsf@web.de> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL=0.141, SPF_HELO_PASS=-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:139650 Archived-At: * Michael Heerdegen [2022-09-27 13:57]: > Eli Zaretskii writes: > > > 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. > > Yes, likely. > > 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. I am manually using the number guessing method: - If there are 12000 lines, I go to middle of that one, like line 6000, somewhere from there up or to bottom, I do M-x eval-region - Then if there is failure, I go to half between x and 6000, if it is in bottom region I go to line 9000 and eval region from 9000 to 12000; - Then if problem is between 6000 - 9000, then I go to to half of it, to line 7500 and again verify 50% of region; That way I arrive fastest to the location. Could that same algorithm be used in Emacs for function to narrow it to lines from X to Y? -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/