From: Anselm Helbig <anselm.helbig+news2009@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Source code navigation in emacs
Date: Wed, 08 Jul 2009 10:00:46 +0200 [thread overview]
Message-ID: <87r5wrd2oh.wl%anselm.helbig+news2009@googlemail.com> (raw)
In-Reply-To: <mailman.2037.1247026972.2239.help-gnu-emacs@gnu.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]
At Tue, 7 Jul 2009 16:53:31 -0700,
n179911 <n179911@gmail.com> wrote:
>
> On Tue, Jul 7, 2009 at 2:29 PM, Dirk-Jan C. Binnema<djcb.bulk@gmail.com> wrote:
> >
> > Hi,
> >
> >>>>>> "n179911" == n179911 <n179911@gmail.com> writes:
> >
> >
> > >>> Can someone please recommend what is the way to setup code navigation
> > >>> in emacs? I have setup xcope.el with cscope run in emacs.
> > >>>
> > >>> But I read here, it said some thing about gnu global with emacs?
> > >>> http://emacs-fu.blogspot.com/2009/01/navigating-through-source-code-using.html
> >
> >
> > >> The most generic way is to just use a tags table, see the manual:
> >
> > >> etags supports more languages than gnu global, and there is an
> > >> etags program coming with exuberant-ctags that supports even
> > >> more. There are alternative, more capable solutions for specific
> > >> programming languages. What are you working with?
> >
> > Anselm, is there any reason to prefer etags over GNU-Global for C/C++? I am
> > quite happy with GNU-Global (I actually wrote the above blogpost) -- in what
> > way would etags be better?
> >
>
> And can you please help me understand why GNU-Global is better than
> xcope.el + cscope for emacs?
As I said, using tags tables is the most generic approach. Support for
it has been in emacs for a long time. Any installation of emacs should
also come with the etags program, which supports many different
languages, compare:
cscope
C, C++
global
C, C++, Yacc, Java and PHP4
etags (emacs 23)
C, Objective C, C++, Java, Fortran, Ada, Cobol, Erlang, Forth, HTML,
LaTeX, Emacs Lisp/Common Lisp, Lua, Makefile, Pascal, Perl, PHP,
Postscript, Python, Prolog, Scheme and most assembler-like syntaxes
etags (exuberant)
Asm, Asp, Awk, Basic, BETA, C, C++, C#, Cobol, Eiffel, Erlang,
Fortran, HTML, Java, JavaScript, Lisp, Lua, Make, Pascal, Perl, PHP,
Python, REXX, Ruby, Scheme, Sh, SLang, SML, SQL, Tcl, Vera, Verilog,
Vim, YACC
It doesn't do fancy stuff, e.g. keeping an index of function
references. That's the kind of thing gnu global and cscope can do for
you, if you're working with a language that they support.
I'm using ruby and javascript at the moment, so I don't have a real
alternative. I should look at CEDET again, though. 8-)
HTH,
Anselm
--
Anselm Helbig
mailto:anselm.helbig+news2009@googlemail.com
next prev parent reply other threads:[~2009-07-08 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1965.1246938924.2239.help-gnu-emacs@gnu.org>
2009-07-07 8:52 ` Source code navigation in emacs Anselm Helbig
2009-07-07 19:20 ` n179911
2009-07-07 21:29 ` Dirk-Jan C. Binnema
2009-07-07 23:53 ` n179911
2009-07-08 19:35 ` Dirk-Jan C. Binnema
[not found] ` <mailman.2099.1247081719.2239.help-gnu-emacs@gnu.org>
2009-07-09 20:25 ` Anselm Helbig
2009-07-10 10:29 ` Sébastien Vauban
[not found] ` <mailman.2037.1247026972.2239.help-gnu-emacs@gnu.org>
2009-07-08 8:00 ` Anselm Helbig [this message]
2009-07-06 5:31 n179911
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5wrd2oh.wl%anselm.helbig+news2009@googlemail.com \
--to=anselm.helbig+news2009@googlemail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.