unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: gtags/ctags/etags/cscope support?
Date: Sat, 23 Mar 2019 21:00:15 +0200	[thread overview]
Message-ID: <83y355o1q8.fsf@gnu.org> (raw)
In-Reply-To: <20190323184544.utmrpin5rkzw56i3@Ergus> (message from Ergus on Sat, 23 Mar 2019 19:45:44 +0100)

> Date: Sat, 23 Mar 2019 19:45:44 +0100
> From: Ergus <spacibba@aol.com>
> Cc: emacs-devel@gnu.org
> 
> >It would indeed be interesting to have a comparison table of features
> >in one place.  Then we could try to figure out what we want to
> >support.  I'm guessing no single tool in its current form will do.
> >
> The comparison already exist; independently of how accurate it is. There
> is a link in the global's page:
> 
> https://github.com/oracle/opengrok/wiki/Comparison-with-Similar-Tools

That doesn't sound too useful to me (does "ctags" there allude to our
etags?), e.g. it doesn't say which languages are supported.  And I'm
not really sure I understand how that comparison will help you in
your quest.

> The other point is that in case of using tramp it is theoretically
> possible to use a remote tags file with the local executable but I am
> not "lispy" enough yet to implement such a thing myself from scratch.

Doesn't visit-tags-table support remote file names?  If it does, you
just visit TAGS that lives on the remote machine, and then the
"normal" etags commands will just work.



  reply	other threads:[~2019-03-23 19:00 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 [this message]
2019-03-23 16:48 ` Konstantin Kharlamov
2019-03-23 18:33 ` Vladimir Sedach

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=83y355o1q8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).