From: David Kastrup <dak@gnu.org>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Edebug and defuns not on top level
Date: Wed, 14 Feb 2007 11:15:49 +0100 [thread overview]
Message-ID: <86abzhm4dm.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <45D2E0B1.6070605@gmail.com> (Lennart Borgman's message of "Wed\, 14 Feb 2007 11\:13\:05 +0100")
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
> If I use something like this
>
> (when my-platform
> (defun my-defun()
> ...
> )
> )
>
> I can not directly evaluate my-defun with edebug-defun. What are the
> recommendations to do in a case like this?
I'd try narrow-to-region.
--
David Kastrup
next prev parent reply other threads:[~2007-02-14 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 10:13 Edebug and defuns not on top level Lennart Borgman (gmail)
2007-02-14 10:15 ` David Kastrup [this message]
2007-02-14 10:25 ` Lennart Borgman (gmail)
2007-02-14 10:29 ` David Kastrup
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=86abzhm4dm.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.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).