From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: gtags/ctags/etags/cscope support?
Date: Sat, 23 Mar 2019 19:48:04 +0300 [thread overview]
Message-ID: <1553359684.26223.1@yandex.ru> (raw)
In-Reply-To: <20190323160624.gz5fducjm3thrb2b@Ergus>
В Сб, мар 23, 2019 at 7:06 ПП (PM), Ergus <spacibba@aol.com>
написал:
> Hi all:
>
> Some days ago Stefan was talking about ebrowse but now it makes me
> think.
>
> 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.
AFAIK ctags and etags share the same format. There's a lot of different
apps that generate TAGS file, e.g. etags, ctags, anjuta-tags; then
there were some old unsupported ctags, but nowadays by ctags usually
implied "universal ctags" which is the maintained version of older
ctags.
I can't answer for the rest of them. But one thing I can tell: tags
stuff is very popular because it allows to share some infrastructure
with Vim. Ofc formats are a bit different, but not very much, and
usually tagging apps can produce both Emacs and Vim formats.
To add even more confusion: nowadays there's an open LSP standard, and
I think it's the future. It supports a lot of different editors, lots
of languages, and is more flexible than tags (in LSP, basically, you
have a separate server running that provides features to editors).
> Is it there any internal support for any of them within emacs? Is the
> ggtags package actively maintained?
> Because I want to invest some time in one of them to improve the
> support
> for tramp and ivy.
>
> Which of them has more potential in your opinion?
>
> Thanks in advance
> Ergus
>
next prev parent reply other threads:[~2019-03-23 16:48 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1553359684.26223.1@yandex.ru \
--to=hi-angel@yandex.ru \
--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 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.