all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: debug-on-entry question
Date: Sun, 19 Jun 2005 11:07:25 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEHHCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <85psui8cfr.fsf@lola.goethe.zz>

    >     change the interactive specification of
    >     `debug-on-entry' to call `function-called-at-point'.
    >
    > Yes. I've suggested this previously. When debugging, you are often
    > in an Emacs-Lisp buffer, and this is useful.

    _If_ you are in an Emacs-Lisp buffer and consequently have the source
    code of the function to be debugged available, edebug-defun is orders
    of magnitude more useful for debugging a particular function.

    debug-on-entry is much less convenient, but can be used without having
    the source at hand.

OK. I take that as an FYI about the usefulness and appropriateness of edebug
in a source-code buffer, but not as an argument not to let `debug-on-entry'
grab the function-at-point in its interactive spec.

  reply	other threads:[~2005-06-19 18:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18 10:03 debug-on-entry question Yoni Rabkin Katzenell
2005-06-18 11:23 ` David Kastrup
2005-06-18 11:47   ` Yoni Rabkin Katzenell
2005-06-19 14:03 ` Juri Linkov
2005-06-19 17:24   ` Drew Adams
2005-06-19 17:48     ` David Kastrup
2005-06-19 18:07       ` Drew Adams [this message]
2005-06-20  4:59     ` Juri Linkov
2005-06-20 15:42       ` Drew Adams
2005-06-21  2:00       ` Richard Stallman
2005-06-20  3:50   ` Richard Stallman
2005-06-20 17:41   ` Lute Kamstra
2005-06-21 16:32     ` Juri Linkov
2005-06-22  3:40       ` Richard M. Stallman
2005-06-22  8:32         ` Lute Kamstra
2005-06-23  0:54           ` Richard M. Stallman
2005-06-22 13:12         ` Juri Linkov
2005-06-23 14:38           ` Drew Adams

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=DNEMKBNJBGPAOPIJOOICGEHHCJAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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 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.