From: Noam Postavsky <npostavs@gmail.com>
To: Tim Fischbach <mail@timfischbach.de>
Cc: 30758@debbugs.gnu.org
Subject: bug#30758: 25.3; Cannot exit minibuffer with C-g when opening file or switching buffers
Date: Fri, 09 Mar 2018 22:05:05 -0500 [thread overview]
Message-ID: <871sgs1vha.fsf@gmail.com> (raw)
In-Reply-To: <CAJXxpwQGR1d65Ev9sn-duc8LZuR1BbMxC_F4Yc4C+cJAnxra2g@mail.gmail.com> (Tim Fischbach's message of "Fri, 09 Mar 2018 09:33:57 +0000")
unarchive 26289
reopen 26289
merge 30758 29063 26289
quit
Tim Fischbach <mail@timfischbach.de> writes:
> I am facing the exact problem described in
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26289
>
> on both Emacs 25.3.2 and 24.5.1 also via `emacs -Q`.
> When running emacs inside the terminal via `emacs -nw` the problem
> does not occur.
Do you see the same symptoms described in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29063#17
I have also noticed that, with toggle-debug-on-quit on, just typing C-g
while in the normal writing buffer will always send me to the debugger on
only one line:
Debugger entered--Lisp error: (quit)
internal-timer-start-idle()
This happens in the broken emacs only, and C-g here does nothing in the
working emacs. Likewise, in the broken emacs, while I am highlighting text
with C-space, C-g will 50% of the time cancel the highlight and 50% of the
time open the above debugger on the timer start function.
next prev parent reply other threads:[~2018-03-10 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 9:33 bug#30758: 25.3; Cannot exit minibuffer with C-g when opening file or switching buffers Tim Fischbach
2018-03-09 18:31 ` Eli Zaretskii
2018-03-10 3:05 ` Noam Postavsky [this message]
2018-03-12 12:48 ` Tim Fischbach
2018-03-12 15:42 ` Glenn Morris
2018-03-12 16:20 ` Tim Fischbach
2018-03-12 18:49 ` Glenn Morris
2018-03-13 1:12 ` Noam Postavsky
2018-03-13 13:14 ` Tim Fischbach
2019-09-29 15:10 ` bug#26289: " Lars Ingebrigtsen
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=871sgs1vha.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=30758@debbugs.gnu.org \
--cc=mail@timfischbach.de \
/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).