From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: chen bin Newsgroups: gmane.emacs.devel Subject: Fwd: [ELPA] New package: mctags Date: Sat, 14 Oct 2017 11:52:10 +1100 Message-ID: References: <87h8v439ub.fsf@gmail.com> <837ew0mupm.fsf@gnu.org> <83mv4wl4yv.fsf@gnu.org> <83zi8vjuxd.fsf@gnu.org> <4478b1dc-9f51-a8da-f989-0348098f6fab@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1507942385 23839 195.159.176.226 (14 Oct 2017 00:53:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Oct 2017 00:53:05 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 14 02:53:01 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e3AhA-0004ct-VY for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 02:52:53 +0200 Original-Received: from localhost ([::1]:52354 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3AhI-0004R7-8a for ged-emacs-devel@m.gmane.org; Fri, 13 Oct 2017 20:53:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3Aga-0004Qj-Vt for emacs-devel@gnu.org; Fri, 13 Oct 2017 20:52:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3AgW-0006Y7-3M for emacs-devel@gnu.org; Fri, 13 Oct 2017 20:52:17 -0400 Original-Received: from mail-it0-x235.google.com ([2607:f8b0:4001:c0b::235]:49015) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e3AgV-0006Xx-T6 for emacs-devel@gnu.org; Fri, 13 Oct 2017 20:52:12 -0400 Original-Received: by mail-it0-x235.google.com with SMTP id c3so13241060itc.3 for ; Fri, 13 Oct 2017 17:52:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=giY5B1yYiGIb62Fv/oikSw5XWg3qeQmsPc1dvYeV3N4=; b=MZcazawfwQ88jyfxJJBGO6unrqRYaFs961UE3eOtSBhKjJ44X5V5wMmOFBoRHdCoKS lFYCxyDFk5b6KsiTVAfJwGVKSxln5vA7KJq31zbDl7dYNWShwUw815xSbzvZZiwhwDhp 3T+j5FuxZ8zg3umby7sQiE9YlWv934I0qhpk3YPmawstLg+BOWqXt1yjivJonl/ZXzsw uEAP0q/Kdx9bddXfcYuftJaH5tXQMi/Ju7v0dMldQyc5FTsWYt1DzOLO1C3HzwmTKFFb pULXR89iu08sB+zcLsn0NllNl3bCwkQQK6/tJlF5NdUvOw83mtyQsLplTtee9B2IFiZQ ox8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=giY5B1yYiGIb62Fv/oikSw5XWg3qeQmsPc1dvYeV3N4=; b=YF1AnF1I0s3AAvBZlqKmRjobCIkb+++YYsJO6GejjZonu+3CLypWd/LZexry0feitV Rg79BjmMbxeUCtw+8qODGIPshe+m/0JN5sgtTRtLzWNzL/OKTogdvIrlhJs6wW7bfQe1 kLwNwFhL3bIYxwOrPrtmcJVEK6Gc+T6p1Gr+kTPQB/1qNQiupE6luVy1N+DYzpb3DpX0 Yz9sb5VXHwgTFUeSGtOrl5c4x3dUf9G6BRzugmHvkNseyeab6h2bV20xWON0RlAtE/OO ahj8SekK1fG5AZwHjHzfIQgmbonLZpddQQcy8tjU2kiG0t/T/SuqiiUOtyGXZG+nJprl rqnw== X-Gm-Message-State: AMCzsaUNFgS8Ut8q8Re8QESs7s+8zMvfOAQWEWvUaJQvg/i2ScDdGo6A ICSaSPayiIacDWEbdi3dKNijf/hzKpr8Mg/8y/U= X-Google-Smtp-Source: AOwi7QBKyzTxA0vPw56hvAXyXwbOfFjXdHt/CfZ41mzQvRobL/kAZxGiZ+NsbDZuIppP3USNmgJwJUL6kNrWRHlS4iI= X-Received: by 10.36.217.206 with SMTP id p197mr4912328itg.45.1507942330939; Fri, 13 Oct 2017 17:52:10 -0700 (PDT) Original-Received: by 10.107.133.90 with HTTP; Fri, 13 Oct 2017 17:52:10 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4001:c0b::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:219471 Archived-At: ---------- Forwarded message ---------- From: chen bin Date: Sat, Oct 14, 2017 at 11:51 AM Subject: Re: [ELPA] New package: mctags To: Dmitry Gutov Sure. I also learned a lot by studying xref code. mctags is targeted on a niche market (web front end developers) while `xref` is a powerful one-for-all package. So they have totally different road map. For example, as a web developer, I prefer mctags to sacrifice precision by fuzzy matching more candidates at the first stage. But `xref` might prefer precision because it's also used by C/Perl developers. I've planed many more features for web front end developers in `mctags`. As I know, there are a few auto-completion packages hosted on ELPA or built in Emacs (complete-symbol, hippie-expand, company-mode, ivy's completion at point). They all serve the users well in different scenarios. For example, I use both hippie-expand and company-mode. hippie-expand to auto-complete words in mini-buffer and company-mode for anything. Even there are some overlapping minor features between xref and mctags, that's not a bad thing. A little bit rival is only good to both packages, and more importantly, it gives the user choices. They have freedom to choose the package fit in their specific need. mctags respects the TAGS created by other programs. So it's impossible mctags to conflicts with other programs. I understand someone has concern about auto-updating which might override existing TAGS. But auto-updating is disabled by default. I also have plan to make auto-updating support any third party programs in the future by allowing users to customize it. Regards, Chen On Fri, Oct 13, 2017 at 11:33 PM, Dmitry Gutov wrote: > On 10/13/17 11:47 AM, Eli Zaretskii wrote: > >>>> 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. > > > We could add filtering by file name and/or line contents to xref buffers > too, though. -- help me, help you. -- help me, help you.