all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: Source code navigation in emacs
Date: Fri, 10 Jul 2009 12:29:08 +0200	[thread overview]
Message-ID: <87tz1kde6j.fsf@mundaneum.com> (raw)
In-Reply-To: 87k52hd2of.wl%anselm.helbig+news2009@googlemail.com

Hello,

>>> And can you please help me understand why GNU-Global is better than
>>> xcope.el + cscope for emacs?
>>
>> I don't know if it's better or not -- I just happened to start with
>> GNU-Global and it worked nice for me. Some of the things that I liked and
>> may (or may not) be available in some of the other tools:
>>
>>  - create a tagfile for a whole subtree (recursively)
>>  - incremental updates
>>  - can be used outside emacs
>>
>> However, GNU-Global only supports C, C++, Yacc, Java en PHP.
>
> Well, GNU global definitely has more features, but if it doesn't
> support the language I'm using, it doesn't do any good for me.

By the way, do know anything that could allow easier code navigation of
(La)TeX files?

Thanks,
  Seb

-- 
Sébastien Vauban


  reply	other threads:[~2009-07-10 10:29 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 [this message]
     [not found]       ` <mailman.2037.1247026972.2239.help-gnu-emacs@gnu.org>
2009-07-08  8:00         ` Anselm Helbig
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=87tz1kde6j.fsf@mundaneum.com \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.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.