From: Eli Zaretskii <eliz@gnu.org>
To: Apocalypse Mystic <apocalypsemystic@gmail.com>
Cc: 29063@debbugs.gnu.org
Subject: bug#29063: C-g not quitting minibuffer
Date: Sat, 04 Nov 2017 10:17:21 +0200 [thread overview]
Message-ID: <83375uv4oe.fsf@gnu.org> (raw)
In-Reply-To: <CAEE2+5CQamkUSOSmeVqea405TGxBcn+U1X1CvPEFjhYzEzYwKw@mail.gmail.com> (message from Apocalypse Mystic on Fri, 3 Nov 2017 21:53:28 -0400)
[Please keep the bug address on the CC list.]
> From: Apocalypse Mystic <apocalypsemystic@gmail.com>
> Date: Fri, 3 Nov 2017 21:53:28 -0400
>
> I just updated my other ubuntu system and it works fine, so I don't know that it will be easy to isolate that way.
> The one thing I do notice that is different between the two systems is that when I toggle-debug-on-quit, and
> then try to quit out of the M-x minibuffer, my broken emacs has one extra line in the debugger print out before
> everything else that is missing from the working emacs:
>
> Debugger entered--Lisp error: (quit)
> internal-timer-start-idle()
> ...
>
> I don't really know the emacs internals or timers that well, but might that mean something like that my C-g's
> are getting eaten by quitting out of a frequently restarting internal-timer-start-idle call? I'm not sure what calls it
> or if that helps any. It may just be normal functioning, but maybe it means something to someone who knows
> emacs better than I do. I notice it is in this description of the same issue:
>
> https://github.com/abo-abo/swiper/issues/922
>
> If I can provide any other information that might be helpful, just let me know.
I guess it would be interesting to know which idle timer was
interrupted by C-g in your case.
next prev parent reply other threads:[~2017-11-04 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 1:55 bug#29063: C-g not quitting minibuffer Apocalypse Mystic
2017-10-30 3:49 ` Eli Zaretskii
2017-10-30 23:47 ` Eric Abrahamsen
[not found] ` <CAEE2+5CQamkUSOSmeVqea405TGxBcn+U1X1CvPEFjhYzEzYwKw@mail.gmail.com>
2017-11-04 8:17 ` Eli Zaretskii [this message]
2017-11-04 15:37 ` Apocalypse Mystic
2017-11-04 15:53 ` Eli Zaretskii
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=83375uv4oe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29063@debbugs.gnu.org \
--cc=apocalypsemystic@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 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.