emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Orgmode <emacs-orgmode@gnu.org>
Subject: Re: IDE tools for maintaining Emacs Lisp programs (Org in particular)
Date: Sat, 21 Apr 2012 11:28:06 -0400	[thread overview]
Message-ID: <87397xp0jd.fsf@gmx.com> (raw)
In-Reply-To: <817gx9vfxb.fsf@gmail.com> (Jambunathan K.'s message of "Sat, 21 Apr 2012 10:29:12 +0530")

Jambunathan K <kjambunathan@gmail.com> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>> For all practical purposes, I find this be sufficient.
>> (global-set-key (kbd "C-c f")
>> 		(lambda ()
>> 		  (interactive)
>> 		  (require 'finder)
>> 		  (let ((thing (intern (thing-at-point 'symbol))))
>> 		    (if (functionp thing)
>> 			(find-function thing)
>> 		      (find-variable thing)))))
>> Put your cursor on a variable or a function, C-c f and you are staring
>> right at the definition of the variable or function.  For this to work,
>> the library defining the function or variable should already be
>> loaded.
> Just discovered this from find-func.el
> (require 'find-func)
> (find-function-setup-keys)
> will install the below keymap for you.

Thanks for pointing this out, I have a feeling the find-func
functionality will quickly become core to my elisp file navigation.

To answer the original question, I also tend towards a minimal setup.  I
do all of my editing directly in elisp source files, and I don't use
tags or etags or anything like that.

I use the describe-function and describe-variable help functions with
tab completion *very* frequently to find functions and variables
relevant to my current task, and to then jump to their source.

When drilling into either a bug or unfamiliar functionality I find
edebug invaluable.  Evaluating functions with a prefix argument "C-u
eval-defun" instruments them for interactive step-by-step evaluation
with edebug.

Also, I highly recommend both paredit and the sexp-edit operations
(kill-sexp, paredit-backward-up, paredit-forward, etc...) to anyone
working on any lisp source code.

Eric Schulte

      reply	other threads:[~2012-04-21 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 20:56 IDE tools for maintaining Emacs Lisp programs (Org in particular) Sebastien Vauban
2012-04-20 23:30 ` Bastien
2012-04-21  4:42 ` Jambunathan K
2012-04-21  4:59   ` Jambunathan K
2012-04-21 15:28     ` Eric Schulte [this message]

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87397xp0jd.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \


* 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


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).