From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 36067@debbugs.gnu.org
Subject: bug#36067: 27.0.50; Edebug leaves undefined RET in minibuffer
Date: Fri, 21 Jun 2019 08:14:19 -0700 [thread overview]
Message-ID: <87pnn70y44.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87muiztno9.fsf@web.de>
Noam Postavsky <npostavs@gmail.com> writes:
> tags 36067 + unreproducible
> quit
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> sorry, no recipe. Quite often when I have used edebug, I think often I
>> killed the session by going to top-level (q), normal RET in the
>> minibuffer doesn't work any more. Hitting the key RET does nothing. I
>> have to restart Emacs (I need to close it with the mouse or something
>> like that).
>
> Do you mean that you're stuck in the minibuffer too? Or just that the
> minibuffer becomes non-functional, while other normal typing still
> works.
>
>> I have no clue why this happens. Dunno if it is my fault. Anyone else
>> seeing this?
>
> 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 may have seen something similar, where there seems to be an cursor in
the minibuffer, sort of like a prompt with no text, but you can't "get
there" to quit the prompt. I've found that `exit-recursive-edit' gets
out of it. Ignore me if this is unrelated...
next prev parent reply other threads:[~2019-06-21 15:14 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
2019-06-21 15:14 ` Eric Abrahamsen [this message]
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=87pnn70y44.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36067@debbugs.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).