unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "funkyj" <funkyj@gmail.com>
Subject: using ebrowse with C code
Date: 14 Sep 2005 17:34:22 -0700	[thread overview]
Message-ID: <1126744462.362087.114500@g43g2000cwa.googlegroups.com> (raw)

first, I'm using emacs 21.3 and the code base I'm working on is written
in C.

Glancing over the new (to me) Ebrowse documentation it looks as if
Ebrowse is quite a bit more powerful than the old etags package.  I'd
like to have the class (struct and typedef) browsing and completion
facilities on typedef names and struct membernames.  The Ebrowse
documentation doesn't appear to talk about how ebrowse might be used to
improve the C language experience...

Is is possible to use ebrowse (or etags for that matter) to provide
more powerful browsing and manipulation of C code?

Am I better off sticking with etags and, perhaps, speedbar?

curiously yours,
  --jfc

             reply	other threads:[~2005-09-15  0:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  0:34 funkyj [this message]
2005-09-21  9:22 ` using ebrowse with C code Klaus Berndl
2005-09-26  7:26   ` funkyj

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=1126744462.362087.114500@g43g2000cwa.googlegroups.com \
    --to=funkyj@gmail.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).