From: chen bin <chenbin.sh@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: mctags
Date: Fri, 13 Oct 2017 00:24:17 +1100 [thread overview]
Message-ID: <CAAE-R+96am1wcTPNyPG34S+hAaUJhpLyYpcRoV4Lb6Ums9mHyA@mail.gmail.com> (raw)
In-Reply-To: <837ew0mupm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
- 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.
[-- Attachment #2: Type: text/html, Size: 2641 bytes --]
next prev parent reply other threads:[~2017-10-12 13:24 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 [this message]
2017-10-12 16:13 ` Eli Zaretskii
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=CAAE-R+96am1wcTPNyPG34S+hAaUJhpLyYpcRoV4Lb6Ums9mHyA@mail.gmail.com \
--to=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.