From: martin rudalics <rudalics@gmx.at>
To: "Jason S. Cornez" <jcornez@ravenpack.com>
Cc: 6585@debbugs.gnu.org
Subject: bug#6585: 23.1; Hang / CPU 100% on background interaction when in minibuffer
Date: Thu, 15 Jul 2010 16:57:40 +0200 [thread overview]
Message-ID: <4C3F21E4.6070404@gmx.at> (raw)
In-Reply-To: <4C3EF97A.5080208@ravenpack.com>
> Now, if start == (selected-window) is the minibuffer, then it should be
> clear that current == (next-window ... 'no-minibuffer ...) will never
> result in (eq start current). And if the buffer that is passed in isn't
> visible then (not found) will never be nil and we are stuck in an
> infinite loop.
Using `next-window' to find all windows is generally unsafe since
windows might get created and deleted in between (in particular the one
you named `start'). Always use `window-list' instead. The doc-string
of `next-window'
If you use consistent values for MINIBUF and ALL-FRAMES, you can use
`next-window' to iterate through the entire cycle of acceptable
windows, eventually ending up back at the window you started with.
is IMHO misleading in this regard.
> So this part is not an emacs problem at all. But I am puzzled as to why
> if this is byte-compiled I can't C-g and break out of this.
>
> I'll fix my code and then the problem goes away. So if you want to
> consider this "not-a-bug", ok. But shouldn't C-g work here?
C-g should work. If it doesn't we have a bug. IIUC the only occurrence
of `switch-to-buffer' is ifdefd out in the source code so there can't be
any harm from an inhibit-quitted call from C. Could you try to run Emacs
in the debugger to find out where it hangs? Or post a self-contained
emacs -Q based recipe here?
martin
next prev parent reply other threads:[~2010-07-15 14:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 14:19 bug#6585: 23.1; Hang / CPU 100% on background interaction when in minibuffer Jason Cornez
2010-07-08 16:52 ` Eli Zaretskii
2010-07-09 7:06 ` Jason S. Cornez
2010-07-14 10:27 ` Jason S. Cornez
[not found] ` <handler.6585.B.12786062373280.ack@debbugs.gnu.org>
2010-07-15 12:05 ` Jason S. Cornez
2010-07-15 14:57 ` martin rudalics [this message]
2010-07-15 15:33 ` Jason S. Cornez
2010-07-16 8:27 ` martin rudalics
2010-07-16 8:39 ` Jason S. Cornez
2010-07-15 15:53 ` Johan Bockgård
2010-07-15 15:59 ` Jason S. Cornez
2010-08-31 6:42 ` Jason S. Cornez
2010-08-31 10:24 ` Stefan Monnier
2010-08-31 10:34 ` Jason S. Cornez
2010-08-31 13:09 ` Stefan Monnier
2010-08-31 15:09 ` Jason S. Cornez
2012-04-10 19:37 ` Stefan Monnier
2010-09-13 13:22 ` bug#6585: Patch welcome? Jason S. Cornez
2010-09-13 15:55 ` Stefan Monnier
2011-11-21 22:54 ` bug#6585: status of patch? Tim Connors
2011-11-22 21:47 ` Stefan Monnier
2011-11-23 7:02 ` Jason S. Cornez
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=4C3F21E4.6070404@gmx.at \
--to=rudalics@gmx.at \
--cc=6585@debbugs.gnu.org \
--cc=jcornez@ravenpack.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 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).