all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* bug#29063: C-g not quitting minibuffer
@ 2017-10-30  1:55 Apocalypse Mystic
  2017-10-30  3:49 ` Eli Zaretskii
  0 siblings, 1 reply; 6+ messages in thread
From: Apocalypse Mystic @ 2017-10-30  1:55 UTC (permalink / raw)
  To: 29063

[-- Attachment #1: Type: text/plain, Size: 3935 bytes --]

1) emacs -Q
2) M-x
3) C-g

"Quit" will flash in the minibuffer, but the cursor will remain trapped
in the minibuffer. C-] will still correctly leave the
minibuffer. Holding down C-g for several seconds will eventually cause
the cursor to correctly leave the minibuffer.

This behavior began within the past week or so, possibly caused by
Ubuntu system updates, as I did not knowingly change any meaningful
Emacs variables or install any Emacs packages.

The issue is similar to those described here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26289

https://emacs.stackexchange.com/questions/24260/quitting-minibufer-works-no-more-in-24-5-1

https://github.com/abo-abo/swiper/issues/922


In GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
 of 2017-09-20 on lcy01-07, modified by Debian
Windowing system distributor `The X.Org Foundation', version 11.0.11804000
System Description: Ubuntu 16.04.3 LTS

Configured using:
 `configure --build x86_64-linux-gnu --prefix=/usr
 --sharedstatedir=/var/lib --libexecdir=/usr/lib
 --localstatedir=/var/lib --infodir=/usr/share/info
 --mandir=/usr/share/man --with-pop=yes
 --enable-locallisppath=/etc/emacs24:/etc/emacs:/usr/local/share/emacs/24.5/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.5/site-lisp:/usr/share/emacs/site-lisp
 --build x86_64-linux-gnu --prefix=/usr --sharedstatedir=/var/lib
 --libexecdir=/usr/lib --localstatedir=/var/lib
 --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes
 --enable-locallisppath=/etc/emacs24:/etc/emacs:/usr/local/share/emacs/24.5/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.5/site-lisp:/usr/share/emacs/site-lisp
 --with-x=yes --with-x-toolkit=gtk3 --with-toolkit-scroll-bars
 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat
 -Werror=format-security -Wall' 'CPPFLAGS=-Wdate-time
 -D_FORTIFY_SOURCE=2' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro''

Important settings:
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Quit [32 times]
Making completion list...

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev
gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums mm-util
help-fns mail-prsvr mail-utils help-mode easymenu time-date tooltip
electric uniquify ediff-hook vc-hooks lisp-float-type mwheel x-win x-dnd
tool-bar dnd fontset image regexp-opt fringe tabulated-list newcomment
lisp-mode prog-mode register page menu-bar rfn-eshadow timer select
scroll-bar mouse jit-lock font-lock syntax facemenu font-core frame cham
georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese hebrew greek romanian slovak czech european ethiopic
indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple
abbrev minibuffer nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote make-network-process
dbusbind gfilenotify dynamic-setting system-font-setting
font-render-setting move-toolbar gtk x-toolkit x multi-tty emacs)

Memory information:
((conses 16 72492 4584)
 (symbols 48 17654 0)
 (miscs 40 36 113)
 (strings 32 9526 3990)
 (string-bytes 1 261039)
 (vectors 16 8984)
 (vector-slots 8 383739 16684)
 (floats 8 64 83)
 (intervals 56 221 4)
 (buffers 960 12)
 (heap 1024 30298 915))

[-- Attachment #2: Type: text/html, Size: 5403 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#29063: C-g not quitting minibuffer
  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>
  0 siblings, 2 replies; 6+ messages in thread
From: Eli Zaretskii @ 2017-10-30  3:49 UTC (permalink / raw)
  To: Apocalypse Mystic; +Cc: 29063

> From: Apocalypse Mystic <apocalypsemystic@gmail.com>
> Date: Sun, 29 Oct 2017 21:55:03 -0400
> 
> 1) emacs -Q
> 2) M-x
> 3) C-g
> 
> "Quit" will flash in the minibuffer, but the cursor will remain trapped
> in the minibuffer. C-] will still correctly leave the
> minibuffer. Holding down C-g for several seconds will eventually cause
> the cursor to correctly leave the minibuffer.

Not reproducible here.

> This behavior began within the past week or so, possibly caused by
> Ubuntu system updates, as I did not knowingly change any meaningful
> Emacs variables or install any Emacs packages.

What did the Ubuntu system updates include?  Maybe with that
information we could do something with this issue.

> The issue is similar to those described here:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26289

Which wasn't reproducible, either.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#29063: C-g not quitting minibuffer
  2017-10-30  3:49 ` Eli Zaretskii
@ 2017-10-30 23:47   ` Eric Abrahamsen
       [not found]   ` <CAEE2+5CQamkUSOSmeVqea405TGxBcn+U1X1CvPEFjhYzEzYwKw@mail.gmail.com>
  1 sibling, 0 replies; 6+ messages in thread
From: Eric Abrahamsen @ 2017-10-30 23:47 UTC (permalink / raw)
  To: 29063

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Apocalypse Mystic <apocalypsemystic@gmail.com>
>> Date: Sun, 29 Oct 2017 21:55:03 -0400
>> 
>> 1) emacs -Q
>> 2) M-x
>> 3) C-g
>> 
>> "Quit" will flash in the minibuffer, but the cursor will remain trapped
>> in the minibuffer. C-] will still correctly leave the
>> minibuffer. Holding down C-g for several seconds will eventually cause
>> the cursor to correctly leave the minibuffer.
>
> Not reproducible here.

FWIW (not much), I get this from time to time. Most recently just this
afternoon, when I was happy to learn the C-] trick. I have yet to come
up with a reproducible recipe.






^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#29063: C-g not quitting minibuffer
       [not found]   ` <CAEE2+5CQamkUSOSmeVqea405TGxBcn+U1X1CvPEFjhYzEzYwKw@mail.gmail.com>
@ 2017-11-04  8:17     ` Eli Zaretskii
  2017-11-04 15:37       ` Apocalypse Mystic
  0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2017-11-04  8:17 UTC (permalink / raw)
  To: Apocalypse Mystic; +Cc: 29063

[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.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#29063: C-g not quitting minibuffer
  2017-11-04  8:17     ` Eli Zaretskii
@ 2017-11-04 15:37       ` Apocalypse Mystic
  2017-11-04 15:53         ` Eli Zaretskii
  0 siblings, 1 reply; 6+ messages in thread
From: Apocalypse Mystic @ 2017-11-04 15:37 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 29063

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

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])

Although calling cancel-timer on the timers does not fix the problem,

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.

On Sat, Nov 4, 2017 at 4:17 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> [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.
>

[-- Attachment #2: Type: text/html, Size: 3073 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#29063: C-g not quitting minibuffer
  2017-11-04 15:37       ` Apocalypse Mystic
@ 2017-11-04 15:53         ` Eli Zaretskii
  0 siblings, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2017-11-04 15:53 UTC (permalink / raw)
  To: Apocalypse Mystic; +Cc: 29063

> 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.





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2017-11-04 15:53 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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

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.