unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hadron Quark <hadronquark@gmail.com>
Subject: Re: OT:cscope/tags
Date: Mon, 04 Dec 2006 12:52:43 +0100	[thread overview]
Message-ID: <v5fybv7u9g.fsf@gmail.com> (raw)
In-Reply-To: 874pscrlkh.fsf@post.rwth-aachen.de

Thorsten Bonow <thorsten.bonow@post.rwth-aachen.de> writes:

>>>>>> "Hadron" == Hadron  <hadronquark@gmail.com> writes:
>
>     Hadron> Anyone here using cscope/etags?
>
>     Hadron> I have used cscope-indexer to index my gtk headers and the linux
>     Hadron> kernel but it is unbelievably slow compared to using emacs tags
>     Hadron> functionality. Is this how it should be? Which of the many available
>     Hadron> cscope packages out there is the right one to use with
>
> Hi,
>
> I use the packaged version coming along with Debian Unstable. Did you try other
> cscope interfaces to decide if it's Emacs or cscope which is slow?

Do you have the entire kernel cscope'd? I use xcscope.

What cscope.el or equivalent do you use? I use xcscope.el. There are
lots of versions around. This was the first one I tried which worked:


; File:         xcscope.el
; RCS:          $RCSfile: xcscope.el,v $ $Revision: 1.14 $ $Date: 2002/04/10 16:59:00 $ $Author: darrylo $
; Description:  cscope interface for (X)Emacs
; Author:       Darryl Okahata
; Created:      Wed Apr 19 17:03:38 2000
; Modified:     Thu Apr  4 17:22:22 2002 (Darryl Okahata) darrylo@soco.agilent.com
; Language:     Emacs-Lisp

There was no emacs package for cscope in /usr/share/doc/cscope/contrib
as part of the Ubuntu distro.

>
> If you can be more specific I can try to reproduce it on my box and we can
> compare the results.
>
> Have you given gtags a shot?

Oh no :) Another tool :( So far I have etags, ctags, semantic &
senator and now cscope. 

A quick google shows gtags to be a faster etags : tags are already fast
enough just not powerful enough. Semantic is just plain buggy and doesn't
seem to have half the options you might need for code navigation.

cscope is the way as far as I can see, if I can find out which of the
many .el packages I should be using.

Thanks for any help.

>
> Toto

-- 

  reply	other threads:[~2006-12-04 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04  9:40 OT:cscope/tags Hadron
2006-12-04 10:40 ` OT:cscope/tags Thorsten Bonow
2006-12-04 11:52   ` Hadron Quark [this message]
2006-12-04 14:43     ` OT:cscope/tags Thorsten Bonow
2006-12-04 20:37       ` OT:cscope/tags Thorsten Bonow
2006-12-05 19:01         ` OT:cscope/tags Hadron Quark
2006-12-05 21:37           ` OT:cscope/tags Thorsten Bonow
2006-12-05 22:37         ` OT:cscope/tags Hadron Quark
2006-12-04 16:31 ` OT:cscope/tags Perry Smith
     [not found] ` <mailman.1509.1165249894.2155.help-gnu-emacs@gnu.org>
2006-12-05 18:58   ` OT:cscope/tags Hadron Quark
2006-12-05 20:19     ` OT:cscope/tags Perry Smith
     [not found]     ` <mailman.1572.1165349985.2155.help-gnu-emacs@gnu.org>
2006-12-05 22:39       ` OT:cscope/tags Hadron Quark
2006-12-06  0:31         ` OT:cscope/tags Perry Smith
     [not found]         ` <mailman.1581.1165365122.2155.help-gnu-emacs@gnu.org>
2006-12-06  1:32           ` OT:cscope/tags Hadron Quark
2006-12-06  3:19             ` OT:cscope/tags Perry Smith

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=v5fybv7u9g.fsf@gmail.com \
    --to=hadronquark@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).