bug#12093: 24.1; ask-user-about-supersession-threat doesn't bind <ESC> <ESC> or <ESC> <ESC> <ESC>

bug#12093: 24.1; ask-user-about-supersession-threat doesn't bind <ESC> <ESC> or <ESC> <ESC> <ESC>

[Richard Copley]

If you're stuck in ask-user-about-supersession-threat's read loop, you
can hit ESC as many times as you like and it doesn't quit out of the
loop. This can be very annoying as it forces you to stop and work out
what state you've got into.

This bug is present since at least Emacs 22.1.

See D.2 (Key Binding Conventions) in the Emacs Lisp manual:
   * Anything that acts like a temporary mode or state that the user can
     enter and leave should define `<ESC> <ESC>' or `<ESC> <ESC> <ESC>'
     as a way to escape.

(But perhaps ask-user-about-supersession-threat should bind just
<ESC>, in order to be reminiscent of y-or-n-p.)

In GNU Emacs 24.1.1 (i386-mingw-nt5.1.2600)
 of 2012-06-10 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENG
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-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 input:
M-x r e p o r t - e m a c s - b u g <return>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
easymenu mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
mailabbrev gmm-utils mailheader sendmail regexp-opt rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mail-utils time-date tooltip ediff-hook
vc-hooks lisp-float-type mwheel dos-w32 disp-table ls-lisp w32-win
w32-vars tool-bar dnd fontset image fringe lisp-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 loaddefs
button faces cus-face files text-properties overlay sha1 md5 base64
format env code-pages mule custom widget hashtable-print-readable
backquote make-network-process multi-tty emacs)

bug#12093: 24.1; ask-user-about-supersession-threat doesn't bind <ESC> <ESC> or <ESC> <ESC> <ESC>

[Chong Yidong]

Richard Copley <rcopley@gmail.com> writes:

> If you're stuck in ask-user-about-supersession-threat's read loop, you
> can hit ESC as many times as you like and it doesn't quit out of the
> loop. This can be very annoying as it forces you to stop and work out
> what state you've got into.
>
> See D.2 (Key Binding Conventions) in the Emacs Lisp manual:
>    * Anything that acts like a temporary mode or state that the user can
>      enter and leave should define `<ESC> <ESC>' or `<ESC> <ESC> <ESC>'
>      as a way to escape.

Fixed in trunk, thanks for the bug report.