unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Sedach <vas@oneofus.la>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: gtags/ctags/etags/cscope support?
Date: Sat, 23 Mar 2019 11:33:21 -0700	[thread overview]
Message-ID: <5177.22674864984$1553366915@news.gmane.org> (raw)
In-Reply-To: <20190323160624.gz5fducjm3thrb2b@Ergus>

> Between global/gtags/ctags/etags/cscope which of them has been (|| will
> be) better supported in emacs. Because there are many packages around
> but I can't estimate their popularity.

I can talk about Cscope. It is a very different tool from the others
mentioned, since it supports only C (the Cscope web page claims it is
useful for C++ and Java, but I think that is being generous).

There are a lot of Cscope interfaces for GNU Emacs. In 2017 I looked
at most of them and concluded that Robert Jarzmik rscope[1] was the
most robust and easiest to work with. In particular, it worked very
well with Tramp.

I wanted something that was based on compilation-mode and followed
modern GNU Emacs conventions (in particular, multi-occur), so I took
Jarzmik's work and made a package called rcscope[2]. I have not
submitted it to ELPA/MELPA yet, because I want to add editing
functionality that works in the same way as wgrep-mode, and clean up
some mistakes I made in how configuration is done, before releasing.
It should be straightforward to add ivy support to the package.

Vladimir

[1] https://github.com/rjarzmik/rscope
[2] https://github.com/vsedach/rcscope



      parent reply	other threads:[~2019-03-23 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 16:06 gtags/ctags/etags/cscope support? Ergus
2019-03-23 16:44 ` Eli Zaretskii
2019-03-23 18:45   ` Ergus
2019-03-23 19:00     ` Eli Zaretskii
2019-03-23 16:48 ` Konstantin Kharlamov
2019-03-23 18:33 ` Vladimir Sedach [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='5177.22674864984$1553366915@news.gmane.org' \
    --to=vas@oneofus.la \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).