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: Fri, 13 Oct 2017 11:47:42 +0300 [thread overview]
Message-ID: <83zi8vjuxd.fsf@gnu.org> (raw)
In-Reply-To: <CAAE-R+8a_mnx_zYFQDFdkj30VLz5i4Fv85ZyJ+sL6zUvQW7UTw@mail.gmail.com> (message from chen bin on Fri, 13 Oct 2017 12:39:54 +1100)
> From: chen bin <chenbin.sh@gmail.com>
> Date: Fri, 13 Oct 2017 12:39:54 +1100
> Cc: emacs-devel@gnu.org
>
> >> - 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?
> I've been using xref for some time. As I can see, it just gives your
> the list of matches in a buffer. It can't filter further with pattern
> or negative pattern or combination of patterns.
The list is usually very short (most of the time, only one candidate),
so the need for sophisticated filtering is quite low.
> But it's totally fine if you use mctags only for code navigation and
> leave TAGS creation to other solutions.
>
> Please note mctags RESPECTS the existing tags file created by other
> solutions. mctags will NOT override existing TAGS created by other
> programs (Makefile, for example) without user's confirmation.
I understand. It just seemed to me that, if we ignore for the moment
the features for creating/updating TAGS, what's left is very little,
and its contribution to the existing functionality is minor. It
doesn't seem to justify a new package.
Maybe a better way forward is to extend etags.el with a few optional
features.
Anyway, these are just my opinions. I'd be interested to hear from
others.
Thanks.
next prev parent reply other threads:[~2017-10-13 8:47 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
2017-10-13 1:39 ` chen bin
2017-10-13 8:47 ` Eli Zaretskii [this message]
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=83zi8vjuxd.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.