From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Slime and Emacs Lisp
Date: Mon, 10 Apr 2006 00:46:39 -0400 [thread overview]
Message-ID: <87wtdyox68.fsf-monnier+gnu.emacs.gnus@gnu.org> (raw)
In-Reply-To: <8664liodk3.fsf@dellbeast.localhost>
>> 5. O'Reilly has a book called something like Extending Emacs or Emacs
>> Lisp Programming - I can't quite remember. It has some handy tips.
> I have "Writing GNU Emacs Extensions" on my shelf which is quite nice.
> But back to being off-topic: Is there some kind of debugger and
> inspector for Elisp like what Slime provides for CL? At least the
> debugger I know from XEmacs is very basic and does not remotely compare
> to Slime's. Any help is greatly appreciated.
Check the Emacs Lisp Manual, looking for "debugger".
I use `edebug'.
Stefan
next prev parent reply other threads:[~2006-04-10 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 19:23 Sébastien Vauban
2006-04-06 21:30 ` Albert Reiner
2006-04-28 18:45 ` Aaron Hsu
2006-04-07 8:32 ` Tim X
2006-04-07 17:13 ` Sébastien Vauban
2006-04-07 17:48 ` Johan Bockgård
2006-04-21 11:23 ` Giacomo Boffi
2006-04-08 5:05 ` Tim X
2006-04-09 17:37 ` Julian Stecklina
2006-04-10 4:46 ` Stefan Monnier [this message]
2006-04-10 8:23 ` Tim X
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=87wtdyox68.fsf-monnier+gnu.emacs.gnus@gnu.org \
--to=monnier@iro.umontreal.ca \
/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 NNTP newsgroup(s).