* Tracing an unwanted raise-frame()
@ 2008-07-11 12:17 Nordlöw
2008-07-11 20:05 ` Johan Bockgård
2008-07-12 16:02 ` Kevin Rodgers
0 siblings, 2 replies; 3+ messages in thread
From: Nordlöw @ 2008-07-11 12:17 UTC (permalink / raw)
To: help-gnu-emacs
Suddenly my Emacs has started to pop-up/raise itself as soon as I
perform a compilation or a debugging event happens. This makes
debugging of graphical applications virtually impossible. So I am
looking for a way to trace this unwanted call to raise-frame(). How
can I do this? Does Emacs have the concept of breakpoints? The problem
of course occurs only with my own add-ons loaded and I don't want to
waste time checking to brute-force trial-and-error check which error
is the cause of the problem.
Thanks in advance,
Nordlöw
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Tracing an unwanted raise-frame()
2008-07-11 12:17 Tracing an unwanted raise-frame() Nordlöw
@ 2008-07-11 20:05 ` Johan Bockgård
2008-07-12 16:02 ` Kevin Rodgers
1 sibling, 0 replies; 3+ messages in thread
From: Johan Bockgård @ 2008-07-11 20:05 UTC (permalink / raw)
To: help-gnu-emacs
Nordlöw <per.nordlow@gmail.com> writes:
> Suddenly my Emacs has started to pop-up/raise itself as soon as I
> perform a compilation or a debugging event happens. This makes
> debugging of graphical applications virtually impossible. So I am
> looking for a way to trace this unwanted call to raise-frame(). How
> can I do this? Does Emacs have the concept of breakpoints? The problem
> of course occurs only with my own add-ons loaded and I don't want to
> waste time checking to brute-force trial-and-error check which error
> is the cause of the problem.
M-x debug-on-entry
--
Johan Bockgård
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Tracing an unwanted raise-frame()
2008-07-11 12:17 Tracing an unwanted raise-frame() Nordlöw
2008-07-11 20:05 ` Johan Bockgård
@ 2008-07-12 16:02 ` Kevin Rodgers
1 sibling, 0 replies; 3+ messages in thread
From: Kevin Rodgers @ 2008-07-12 16:02 UTC (permalink / raw)
To: help-gnu-emacs
Nordlöw wrote:
> Suddenly my Emacs has started to pop-up/raise itself as soon as I
> perform a compilation or a debugging event happens. This makes
> debugging of graphical applications virtually impossible. So I am
> looking for a way to trace this unwanted call to raise-frame(). How
> can I do this? Does Emacs have the concept of breakpoints? The problem
> of course occurs only with my own add-ons loaded and I don't want to
> waste time checking to brute-force trial-and-error check which error
> is the cause of the problem.
C-h v special-display-buffer-names
C-h v special-display-regexps
--
Kevin Rodgers
Denver, Colorado, USA
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-07-12 16:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-11 12:17 Tracing an unwanted raise-frame() Nordlöw
2008-07-11 20:05 ` Johan Bockgård
2008-07-12 16:02 ` Kevin Rodgers
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).