From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Making Emacs Lisp easier to debug Date: Sun, 12 Nov 2023 12:08:48 +0000 Message-ID: References: <83fs1cwnnv.fsf@gnu.org> <83edgwwge0.fsf@gnu.org> <831qcwwa7v.fsf@gnu.org> <83v8a8uqeo.fsf@gnu.org> <83il67v3t1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17616"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 12 13:10:02 2023 Return-path: Envelope-to: ged-emacs-devel@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 1r29Ht-0004OW-G1 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Nov 2023 13:10:01 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r29Gu-0003RF-Pi; Sun, 12 Nov 2023 07:09:01 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r29Gt-0003R5-9y for emacs-devel@gnu.org; Sun, 12 Nov 2023 07:08:59 -0500 Original-Received: from mail.muc.de ([193.149.48.3]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r29Gp-0006IV-SL for emacs-devel@gnu.org; Sun, 12 Nov 2023 07:08:59 -0500 Original-Received: (qmail 97446 invoked by uid 3782); 12 Nov 2023 13:08:52 +0100 Original-Received: from acm.muc.de (pd953a91f.dip0.t-ipconnect.de [217.83.169.31]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 12 Nov 2023 13:08:52 +0100 Original-Received: (qmail 16815 invoked by uid 1000); 12 Nov 2023 12:08:48 -0000 Content-Disposition: inline In-Reply-To: <83il67v3t1.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.3; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312653 Archived-At: Hello, Eli. On Sun, Nov 12, 2023 at 09:17:14 +0200, Eli Zaretskii wrote: > > Date: Sat, 11 Nov 2023 19:55:29 +0000 > > Cc: emacs-devel@gnu.org > > From: Alan Mackenzie [ .... ] > > Must you be so aggressive, Eli? > It isn't aggression, it's frustration. I have, as you might imagine, > very little time to waste on pointless discussions, so I get > frustrated when, after no less than 3 messages of me trying to help > you solve some problem you seem to be raising, it turns out you have > something very different in mind, which you didn't clearly state until > now. > Please try to describe the issue more clearly and comprehensively next > time, and save me and others from wasting efforts on looking up > solutions for problems you seem to raise, solutions you don't really > mean to use, because you are actually looking for something very > different. In this thread, we have not been communicating effectively. I have clearly failed to get my idea across to you, and on my side, I have not been able to relate what you have said to what I tried to say. I'm sorry about this. I will examine the thread again, and try to work out how I could have done better, in the hope that next time it _will_ be better. I can always try to implement my idea, and then it will only be my own time. But I've got plenty of other things to do at the moment, so this won't be happening soon. [ .... ] > > > > Also, as I mentioned, it[jit-lock-debug-mode]'s not working for > > > > me at the moment. It gives the impression of being an unfinished > > > > piece of code. > > > Then how about fixing the problems there before talking about these > > > far-reaching ideas? Surely, jit-lock-debug-mode is much closer to a > > > satisfactory solution than the ideas of "re-entering redisplay"? I spent some time on jit-lock-debug-mode last night, and bug #67116 "byte-comp-let: reversing the order of evaluation of the clauses CAN make a difference." resulted from that. I managed to get jit-lock-debug-mode working by replacing a `let' by a `let*'. So there will probably be a fix for jit-lock-debug-mode committed soon, whether from Stefan or from me. [ .... ] -- Alan Mackenzie (Nuremberg, Germany).