all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 17:53:00 +0200	[thread overview]
Message-ID: <83ineqt50j.fsf@gnu.org> (raw)
In-Reply-To: <CAEE2+5C2q0GDnE4Mg3WL9FR-CGXXRUeVADy=JZTfG5Zm+XXmqw@mail.gmail.com> (message from Apocalypse Mystic on Sat, 4 Nov 2017 11:37:38 -0400)

> From: Apocalypse Mystic <apocalypsemystic@gmail.com>
> Date: Sat, 4 Nov 2017 11:37:38 -0400
> Cc: 29063@debbugs.gnu.org
> 
> timer-idle-list
> 
> working emacs:
> ([nil 0 0 500000 t jit-lock-context-fontify nil idle 0])
> 
> broken emacs:
> ([nil 0 0 500000 t jit-lock-context-fontify nil idle 0] [nil 0 0 500000 0.5 blink-cursor-start nil idle 0])

Both are normal.

> 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. In the working emacs, of course, it cancels
> the highlight 100% of the time.

I cannot reproduce either of these strange issues.  I tried on 2
different systems, with the same negative result.





      reply	other threads:[~2017-11-04 15:53 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
2017-11-04 15:37       ` Apocalypse Mystic
2017-11-04 15:53         ` Eli Zaretskii [this message]

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=83ineqt50j.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.