unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: robert.thorpe@antenova.com
Subject: Re: Extensions to make C/C++ development easier?
Date: 12 Sep 2006 08:28:02 -0700	[thread overview]
Message-ID: <1158074882.156444.264290@d34g2000cwd.googlegroups.com> (raw)
In-Reply-To: <87odto6nvs.fsf@kip.sateh.com>

Stefan Arentz wrote:
> What are the favorite extensions here for making C/C++ development
> easier?
>
> I'm used to a Java IDE with symbol completion,

For all completion I use M-/ which works in most cases.  Explore the
variables around abbrev and dabbrev to customize these things the way
you want them.

> lookup of
> documentation,

In Emacs that is C-h C-i.  It drops you into the relevant info files.
If you're using Windows where the info file tree isn't populated then
try downloading them from the web.  The Glibc manual is the most useful
if you're doing C.

For lookup of functions I use M-. and etags.  I put "etags *.c *.h"
into the build system for this.

> completion on structs/classes, etc.

That isn't available in standard Emacs.  There is a mode available as
part of ECB which is a package you can download, I've never used it
myself.

Ebrowse, which comes with Emacs, can be useful for C++.

      parent reply	other threads:[~2006-09-12 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 10:01 Extensions to make C/C++ development easier? Stefan Arentz
2006-09-10 10:43 ` Thorsten Bonow
2006-09-10 15:19   ` Stefan Arentz
2006-09-11 23:48     ` Benjamin Rutt
2006-09-12 15:28 ` robert.thorpe [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=1158074882.156444.264290@d34g2000cwd.googlegroups.com \
    --to=robert.thorpe@antenova.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 read-only IMAP folder(s) and NNTP newsgroup(s).