- If there are multiple matches, you can filter the candidates in candidate
window.
- the tags file is automatically created in current project. . BTW, project
root is automatically detected if you use git/svn/hg
- if no match found, fallback to `mctags-grep` to grep in current project.
So you should always found matched string
- Improvement on performance (for example, ripgrep is automatically used as
grep program if installed. GNU grep is fallback grep program)
- tags file could be automatically updated when user save current file.
There is algorithm behind



On Thu, Oct 12, 2017 at 11:11 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Chen Bin <chenbin.sh@gmail.com>
> > Date: Thu, 12 Oct 2017 22:05:16 +1100
> >
> > I developed a package using Ctags. https://github.com/redguardtoo
> /mctags/
> >
> > I would like this package be accepted by ELPA.
> >
> > I'm the only developer of this package which is only dependent on
> > package counsel. Counsel is already accepted by ELPA.
> >
> > I've Emacs signed Copyright Papers when contributing company-mode,
> > https://github.com/company-mode/company-mode/pull/13
> >
> > My situation is not changed.
> >
> > Here is summary of mctags:
> >
> > Fast and complete Ctags solution.
> >
> > Usage:
> >   "M-x mctags-find-tag-at-point" to navigate.  This command will also
> >   run `mctags-scan-code' automatically if tags file is not built yet.
> >
> >   "M-x mctags-scan-code" to create tags file
> >   "M-x mctags-grep" to grep
>
> Can you please tell how is this package different from the built-in
> etags.el package?
>
> Thanks.
>



-- 
help me, help you.