From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: gazally@runbox.com, 33201@debbugs.gnu.org, darkfeline@felesatra.moe
Subject: bug#33201: 26.1; Edebug doesn't work on closures with edebug-unwrap-results
Date: Thu, 01 Nov 2018 20:15:41 +0200 [thread overview]
Message-ID: <83sh0khdf6.fsf@gnu.org> (raw)
In-Reply-To: <20181101100056.GA4504@ACM> (message from Alan Mackenzie on Thu, 1 Nov 2018 10:00:56 +0000)
> Date: Thu, 1 Nov 2018 10:00:56 +0000
> From: Alan Mackenzie <acm@muc.de>
> Cc: 33201@debbugs.gnu.org
>
> > > This fix could probably be backported to the emacs-26 branch, but how
> > > important is it? What were you actually trying to do when you uncovered
> > > this bug?
>
> > I don't remember. I have encountered this error multiple times before
> > and given up debugging something. Since one generally runs into bugs
> > when doing work (that is not hacking on Emacs itself), it's helpful to
> > be able to debug with minimal obstruction, otherwise it becomes an
> > unjustifiable distraction from the main task.
>
> OK, it sounds like it's a major problem.
It does? Why?
> @Gemini: The patch below is a (small) portion of
> e09120d68694272ea5efbe13b16936b4382389d8 from 2018-06-19, the commit that
> introduced Backtrace Mode. Can you see anything against applying this
> commit to the emacs-26 branch to fix this bug?
I can: it's quite complex, and even includes gratuitous refactoring of
'cond' as 'pcase'.
next prev parent reply other threads:[~2018-11-01 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 6:49 bug#33201: 26.1; Edebug doesn't work on closures with edebug-unwrap-results Allen Li
[not found] ` <mailman.3074.1540882208.1284.bug-gnu-emacs@gnu.org>
2018-10-31 15:06 ` Alan Mackenzie
2018-11-01 3:53 ` Allen Li
2018-11-01 10:00 ` Alan Mackenzie
2018-11-01 18:15 ` Eli Zaretskii [this message]
2018-11-01 19:59 ` Alan Mackenzie
2018-11-01 20:18 ` Eli Zaretskii
2018-11-01 23:06 ` Gemini Lasswell
2018-11-02 7:13 ` Allen Li
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sh0khdf6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33201@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=darkfeline@felesatra.moe \
--cc=gazally@runbox.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.