Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Sébastien Vauban" <ewgeocaufsfb@spammotel.com>
Subject: Re: Slime and Emacs Lisp
Date: Fri, 07 Apr 2006 17:13:23 GMT	[thread overview]
Message-ID: <87u095e2bu.fsf@missioncriticalit.com> (raw)
In-Reply-To: <8764lleqgk.fsf@tiger.rapttech.com.au>

Hello,

>> But my ultimate goal would be to try enjoying all the features
>> of Slime for debugging Emacs Lisp code I want to maintain...
>>
>> And, *not* being an expert at all in both languages, I don't
>> know if their differences are so big it's purely impossible to
>> do what I want, or if it's still possible to debug Emacs Lisp
>> code with Slime/CLisp?
>
> Please note this is not the right group for this question. Try
> gnu.emacs.help. 

Sorry, you're right. Stupid mistake.


> Slime is designed for working with common Lisp, which is a different
> beastie to Emacs Lisp. Emacs has a pretty good in-built debugging
> capabilities and a much closer integration than you would get with
> slime even if you could get slime to work with it. 

Can you be a bit more specific about which environment you use
to do so?

For example, how do you get the display of a function's
arguments list in the minibuffer?  Very very useful.

How do you localize source code?  Ctags, Etags, ...?

Thanks for the help,
  Seba

-- 
Sébastien Vauban

  reply	other threads:[~2006-04-07 17:13 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 [this message]
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
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=87u095e2bu.fsf@missioncriticalit.com \
    --to=ewgeocaufsfb@spammotel.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.
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).