emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: IDE tools for maintaining Emacs Lisp programs (Org in particular)
Date: Fri, 20 Apr 2012 22:56:24 +0200	[thread overview]
Message-ID: <80y5pqm8av.fsf@somewhere.org> (raw)


This is a bit OT, but I'd be interested by learning how to get a better
environment for editing ELisp code.

Currently, the only friends I have are ElDoc and C-h f/v for navigation to
symbol definitions. This is rather primitive, isn't it?

When I see what CEDET and ECB seem to offer -- though I'm not using them, not
coding in C/C++, etc. -- , I'm quite jealous.

Questions that I have:

- Do you use TAGS?
- If yes, why don't we make TAGS from within the Makefile?
- If yes, which ones: Emacs-style TAGS, Exuberant Ctags, GNU GLOBAL tags?
- What do you use to jump from the point where a symbol is used to the point
  where a symbol is defined (other than using C-h f/v)?
- How do you return to your previous location?
- Are you able to use CEDET/ECB for Emacs Lisp?
- Are you willing to share extract of your interesting configuration scraps?

Best regards,

Sebastien Vauban

             reply	other threads:[~2012-04-20 20:56 UTC|newest]

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

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=80y5pqm8av.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


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