From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Danil Orlov <zargener@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: From etags to ctags?
Date: Wed, 04 Jun 2014 21:11:27 -0400 [thread overview]
Message-ID: <538FC3BF.7040101@siege-engine.com> (raw)
In-Reply-To: <20140604142339.GA27417@debian>
On 06/04/2014 10:23 AM, Danil Orlov wrote:
> Emacs now support only etags format directly. But this format does not support storage of extended information about symbols, like scoping and inheritance data. But Exuberant Ctags can gather such data.
>
> And if such information will be presented in tags, it will be possible make smarter completion for company-mode and auto-complete-mode. Without creating a parser in elisp, like in js2-mode.
>
> How do you think, does it make sense to create direct support of ctags format, like it done for etags now?
The command "semantic-load-enable-secondary-ectags-support" will enable
use of Exuberent CTags to be used as a parser using Semantic for C/C++.
The extended parsing information can be used for C/C++ so that files
not in buffers are parsed without loading them into Emacs. That, in
turn, can be used with the smart completion engine available via the
CEDET/semantic system.
I tend not to use it because ctags parser isn't very good, and it fails
to parse information about templates and other language features needed
in more complex applications.
There is also "semantic-load-enable-primary-ectags-support" to add
semantic support via ctags for 8 other modes.
The core parse for ctags isn't too complex so of someone wanted to use
it to do something else, that probably wouldn't be too hard. As a
bonus, said code would then also work with other kinds of CEDET/semantic
parsers.
Eric
prev parent reply other threads:[~2014-06-05 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 14:23 From etags to ctags? Danil Orlov
2014-06-04 18:00 ` Stefan Monnier
2014-06-04 18:44 ` John Yates
2014-06-04 19:40 ` Stefan Monnier
2014-06-06 19:01 ` John Yates
2014-06-05 1:11 ` Eric M. Ludlam [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538FC3BF.7040101@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=zargener@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.
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.