From: Ken Goldman <kgold@watson.ibm.com>
To: help-gnu-emacs@gnu.org
Subject: Re: What are your favorite C/C++ tools for emacs?
Date: Wed, 20 Jun 2007 16:22:43 -0400 [thread overview]
Message-ID: <467adb6c$1@news.greennet.net> (raw)
In-Reply-To: <87hcp8fhs2.fsf@kip.sateh.com>
Not limited to C
- keyboard macros are #1.
- dabbrev-expand saves a lot of typing and typos for long variable and
function names (my style)
- egrep for finding where a function or variable is used and stepping
through matches
- autorevert for looking at debugger trace files in real time
- integration with CVS and SVN
- speedbar
Specifically for C:
- c-macro-expand, especially when maintaining code with a lot of clever
uncommented macros (not my style)
Stefan Arentz wrote:
>
> I'm interested to hear from others what their favorite tools or
> extensions are for doing C/C++ development with emacs. I know there is
> a lot on the emacs wiki but I find it more interesting to hear it here
> from people.
prev parent reply other threads:[~2007-06-20 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 8:03 What are your favorite C/C++ tools for emacs? Stefan Arentz
2007-06-16 16:36 ` Hadron
2007-06-20 20:22 ` Ken Goldman [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:
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='467adb6c$1@news.greennet.net' \
--to=kgold@watson.ibm.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).