From: "Drew Adams" <drew.adams@oracle.com>
To: 12521@debbugs.gnu.org
Subject: bug#12521: 24.2.50; normal buffer starts acting like minibuffer, has `InactiveMinibuffer' lighter
Date: Wed, 26 Sep 2012 08:54:07 -0700 [thread overview]
Message-ID: <E021CC32E782443280B194E6B3E3D2CD@us.oracle.com> (raw)
Sorry, I have no recipe. If this helps, great; if not, please close.
I have no idea how it happened, but I've found myself with what was an
EmacsLisp buffer (i.e., code) suddenly acting as if it were a
minibuffer. The modeline lighter includes `InactiveMinibuffer', and
when I click mouse-1 in the buffer it pops up the *Messages* buffer.
The buffer still has the Emacs-Lisp code in it, and it is marked
unmodified and looks normal (except that it is no longer font-locked for
Emacs-Lisp mode).
Again, I have no idea what happened, how, or why. Here is the output
from `C-h l', but I doubt it will help (why oh why can't users customize
the length of its output?).
C-s C-a C-s C-s C-s C-s C-s C-s C-s C-r C-r C-r C-a
<C-S-down-mouse-1> <C-S-mouse-1> <C-S-double-down-mouse-1>
<C-S-double-mouse-1> <C-S-triple-down-mouse-1> <C-S-triple-mouse-1>
<down-mouse-1> <mouse-1> M-x l o a d - f <return> <return>
<down-mouse-1> <mouse-1> M-x d e b u g - o n <return>
<return> <down-mouse-1> <mouse-movement> <mouse-1>
M-x M-p M-p M-p <return> <help-echo> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> <help-echo>
<help-echo> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> c <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> c <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> c <switch-frame>
<switch-frame> d <switch-frame> <switch-frame> d <switch-frame>
<switch-frame> <help-echo> <help-echo> d d d d c d
d d c d c d c d c d c d <down-mouse-1> <mouse-movement>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> C-a d d c d d d d d d d <help-echo> c c <tab>
<S-tab> <S-tab> C-g C-g C-g C-g C-g <down-mouse-1>
<mouse-1> <switch-frame> M-x M-p <return> <switch-frame>
<switch-frame> <help-echo> <help-echo> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <double-down-mouse-1> <double-mouse-1> <down-mouse-1>
<mouse-1> <down-mouse-1> <mouse-1> <down-mouse-1> <mouse-1>
q <down-mouse-1> <mouse-1> <switch-frame> <down-mouse-1>
<mouse-1> <switch-frame> C-h l
I was in the debugger when this started happening. Here is some of what
is at the end of *Messages*:
... (more of the same)...
Entering debugger...
Continuing.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Proceeding, will debug on next eval or call.
Entering debugger...
Continuing.
Entering debugger...
Continuing.
Computing completion candidates... [3 times]
Quit [4 times]
Entering debugger...
Back to top level.
Type "q" to delete help frame, M-x scroll-up to scroll help.
Mark set [2 times]
Saved text until "mouse-1>
<mouse-1> <switch-frame> C-h l
"
In GNU Emacs 24.2.50.1 (i386-mingw-nt5.1.2600)
of 2012-09-17 on MARVIN
Bzr revision: 110062 cyd@gnu.org-20120917054104-r93rtwkrtva73ewe
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --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
-ID:/devel/emacs/libs/libiconv-1.13.1-1-dev/include
-ID:/devel/emacs/libs/libxml2-2.7.8/include/libxml2'
reply other threads:[~2012-09-26 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E021CC32E782443280B194E6B3E3D2CD@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12521@debbugs.gnu.org \
/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.