unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Making Emacs Lisp easier to debug
Date: Sun, 12 Nov 2023 12:08:48 +0000	[thread overview]
Message-ID: <ZVDAUCOpjBpIB21m@ACM> (raw)
In-Reply-To: <83il67v3t1.fsf@gnu.org>

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 <acm@muc.de>

[ .... ]

> > 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).



  reply	other threads:[~2023-11-12 12:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 20:56 Making Emacs Lisp easier to debug Alan Mackenzie
2023-11-11  6:52 ` Eli Zaretskii
2023-11-11  9:01   ` Ihor Radchenko
2023-11-11 11:04   ` Alan Mackenzie
2023-11-11 11:10     ` Eli Zaretskii
2023-11-11 12:10       ` Alan Mackenzie
2023-11-11 13:47         ` Eli Zaretskii
2023-11-11 14:56           ` Alan Mackenzie
2023-11-11 16:01             ` Eli Zaretskii
2023-11-11 17:23               ` Alan Mackenzie
2023-11-11 17:54                 ` Eli Zaretskii
2023-11-11 19:55                   ` Alan Mackenzie
2023-11-12  7:17                     ` Eli Zaretskii
2023-11-12 12:08                       ` Alan Mackenzie [this message]
2023-11-12 12:28                         ` Eli Zaretskii
2023-11-13 18:20                       ` XY Problems (tangent, related to common discussion issue here) chad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZVDAUCOpjBpIB21m@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).