From: Eli Zaretskii <eliz@gnu.org>
To: chen bin <chenbin.sh@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: mctags
Date: Thu, 12 Oct 2017 19:13:12 +0300 [thread overview]
Message-ID: <83mv4wl4yv.fsf@gnu.org> (raw)
In-Reply-To: <CAAE-R+96am1wcTPNyPG34S+hAaUJhpLyYpcRoV4Lb6Ums9mHyA@mail.gmail.com> (message from chen bin on Fri, 13 Oct 2017 00:24:17 +1100)
> From: chen bin <chenbin.sh@gmail.com>
> Date: Fri, 13 Oct 2017 00:24:17 +1100
>
> - If there are multiple matches, you can filter the candidates in candidate window.
I think xref-find-definitions, when it uses the etags back-end,
already supports that, doesn't it?
> - the tags file is automatically created in current project.
Yes, but AFAICT, the package uses a somewhat naïve way of generating
TAGS, in effect passing all the non-trivial file names to etags. Some
projects might use more sophisticated methods, for example see what
src/Makefile does in Emacs to tag both the Lisp and the C names of the
Emacs primitives.
> - if no match found, fallback to `mctags-grep` to grep in current project. So you should always found matched
> string
But the matches found this way are not necessarily definitions, they
can be references.
> - Improvement on performance (for example, ripgrep is automatically used as grep program if installed. GNU
> grep is fallback grep program)
Well, finding a tag via etags.el doesn't require Grep at all.
> - tags file could be automatically updated when user save current file.
Is this really a good idea? Updating TAGS means you need also revisit
it, which could be a problem in some complex setups, when there's more
than one tag table active at the same time. OTOH, etags.el is written
in a way that makes frequent updates of TAGS unnecessary.
next prev parent reply other threads:[~2017-10-12 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 11:05 [ELPA] New package: mctags Chen Bin
2017-10-12 12:11 ` Eli Zaretskii
2017-10-12 13:24 ` chen bin
2017-10-12 16:13 ` Eli Zaretskii [this message]
2017-10-13 1:39 ` chen bin
2017-10-13 8:47 ` Eli Zaretskii
2017-10-13 12:24 ` chen bin
2017-10-13 12:33 ` Dmitry Gutov
[not found] ` <CAAE-R+-Xxm3x5_u9jMO243SqfwaYfQs6XC=p1T0XQaAeFgy+dg@mail.gmail.com>
2017-10-14 0:52 ` Fwd: " chen bin
2017-10-13 13:42 ` Stefan Monnier
2017-10-21 19:59 ` Tom Tromey
2017-10-21 20:43 ` Stefan Monnier
2017-10-25 15:11 ` Tom Tromey
2017-11-12 3:19 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2017-10-07 1:39 Chen Bin
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=83mv4wl4yv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=chenbin.sh@gmail.com \
--cc=emacs-devel@gnu.org \
/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.