From: Michael Heerdegen <michael_heerdegen@web.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 36067@debbugs.gnu.org
Subject: bug#36067: 27.0.50; Edebug leaves undefined RET in minibuffer
Date: Tue, 09 Jul 2019 04:08:05 +0200 [thread overview]
Message-ID: <87d0ikrmd6.fsf@web.de> (raw)
In-Reply-To: <877e9f9e86.fsf@web.de> (Michael Heerdegen's message of "Fri, 21 Jun 2019 16:59:05 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> > Don't think I've ever seen that before. I know the 'transient'
> > package (which magit now uses for its popup UI), can have a bad
> > interaction with edebug when trying to debug its code. I think it's
> > due to how it messes with transient keymaps in post/pre comman
> > hooks. Maybe you have something similar happen here?
>
> I'll try to find out when I see this the next time.
I saw it again. This time indeed a left over transient-map was the
culprit. The transient-map had been installed with `set-transient-map'
with a KEEP-PRED that should have been failing, but somehow, due to the
interaction with edebug, or just the recursive edit, the transient map
stayed alive, I guess the KEEP-PRED was not tested anymore, but I'm not
sure. It's not easy to reproduce the issue at will, so I have a hard
time to find out more.
Michael.
next prev parent reply other threads:[~2019-07-09 2:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 2:20 bug#36067: 27.0.50; Edebug leaves undefined RET in minibuffer Michael Heerdegen
2019-06-21 10:14 ` Noam Postavsky
2019-06-21 14:59 ` Michael Heerdegen
2019-07-09 2:08 ` Michael Heerdegen [this message]
2019-06-21 15:14 ` Eric Abrahamsen
2019-06-21 15:59 ` Michael Heerdegen
2019-06-22 8:22 ` martin rudalics
2021-08-10 16:11 ` Lars Ingebrigtsen
2024-04-21 4:24 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-21 6:02 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87d0ikrmd6.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=36067@debbugs.gnu.org \
--cc=npostavs@gmail.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 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).