unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* Cannot edebug in tabbar.el.
@ 2015-06-25 17:27 BobD
  2015-06-26 19:00 ` Stefan Monnier
  0 siblings, 1 reply; 2+ messages in thread
From: BobD @ 2015-06-25 17:27 UTC (permalink / raw)
  To: help-gnu-emacs

Using emacs GNU Emacs 24.5.1 (i686-pc-mingw32) of 2015-04-11 on LEG570
tabbar.el:
  ;; Revision: $Id: tabbar.el,v 1.7 2009/03/02 21:02:34 davidswelt Exp $
  tabbar-version "2.0"

I ran edebug-defun in several tabbar functions, e.g. (tabbar-buffer-groups).
No breaks when function entered.
I added (message "Entered tabbar-buffer-groups") to (tabbar-buffer-groups).
The message appears dozens of times.

I tried this with "-*-no-byte-compile: t; -*-" present and absent.  No difference.

I was able to get a couple of functions to break into the debugger.

Any thoughts on how tabbar.el is selectively blocking edebug?


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

* Re: Cannot edebug in tabbar.el.
  2015-06-25 17:27 Cannot edebug in tabbar.el BobD
@ 2015-06-26 19:00 ` Stefan Monnier
  0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2015-06-26 19:00 UTC (permalink / raw)
  To: help-gnu-emacs

> Any thoughts on how tabbar.el is selectively blocking edebug?

Edebug can't be used when evaluating code during redisplay (because
that would require redisplaying during the redisplay).  So most likely
the code you can't edebug is run during redisplay (at its beginning,
when (re)computing the header-line that should be displayed).


        Stefan


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

end of thread, other threads:[~2015-06-26 19:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-25 17:27 Cannot edebug in tabbar.el BobD
2015-06-26 19:00 ` Stefan Monnier

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