unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: BobD <daycandle@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Cannot edebug in tabbar.el.
Date: Thu, 25 Jun 2015 10:27:55 -0700 (PDT)	[thread overview]
Message-ID: <5f0aabb7-f2fc-4644-8ccd-82979e71d4f2@googlegroups.com> (raw)

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?


             reply	other threads:[~2015-06-25 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 17:27 BobD [this message]
2015-06-26 19:00 ` Cannot edebug in tabbar.el Stefan Monnier

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=5f0aabb7-f2fc-4644-8ccd-82979e71d4f2@googlegroups.com \
    --to=daycandle@gmail.com \
    --cc=help-gnu-emacs@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. 
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).