From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#20629: 25.0.50; Regression: TAGS broken, can't find anything in C++ files. Date: Fri, 29 May 2015 23:01:13 +0300 Message-ID: <5568C589.5000405@yandex.ru> References: <555EC552.5010600@swipnet.se> <55606A8F.1020109@swipnet.se> <55606CC7.3010401@yandex.ru> <55606F70.10605@swipnet.se> <83twv31jzg.fsf@gnu.org> <83pp5r1hdx.fsf@gnu.org> <83mw0v1e5n.fsf@gnu.org> <83lhgczo16.fsf@gnu.org> <55639175.9090005@yandex.ru> <83fv6kysjf.fsf@gnu.org> <556447EF.3050103@yandex.ru> <83bnh7z8c5.fsf@gnu.org> <5564C2C7.5050909@yandex.ru> <837frvywfn.fsf@gnu.org> <55650812.60909@yandex.ru> <831ti2yu1a.fsf@gnu.org> <5565E28A.5040507@yandex.ru> <83wpzuxbtd.fsf@gnu.org> <5565E8AB.5020107@yandex.ru> <83r3q2xa3q.fsf@gnu.org> <5566583F.7020503@yandex.ru> <83h9qxxvo4.fsf@gnu.org> <5566EC49.8010907@yandex.ru> <837frsycly.fsf@gnu.org> <5567351E.7020006@yandex.ru> <83zj4owthp.fsf@gnu.org> <5567AE52.1000600@yandex.ru> <83fv6fx0nk.fsf@gnu.org> <55687241.5030200@yandex.ru> <83617bw84o.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1432929761 9690 80.91.229.3 (29 May 2015 20:02:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 May 2015 20:02:41 +0000 (UTC) Cc: 20629@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 29 22:02:31 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YyQUA-00067B-Qe for geb-bug-gnu-emacs@m.gmane.org; Fri, 29 May 2015 22:02:30 +0200 Original-Received: from localhost ([::1]:37611 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyQUA-0007C3-2M for geb-bug-gnu-emacs@m.gmane.org; Fri, 29 May 2015 16:02:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyQTn-0006ju-EE for bug-gnu-emacs@gnu.org; Fri, 29 May 2015 16:02:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyQTi-0006c2-F9 for bug-gnu-emacs@gnu.org; Fri, 29 May 2015 16:02:07 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:50905) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyQTi-0006by-9E for bug-gnu-emacs@gnu.org; Fri, 29 May 2015 16:02:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YyQTi-0000vQ-2f for bug-gnu-emacs@gnu.org; Fri, 29 May 2015 16:02:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 29 May 2015 20:02:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20629 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20629-submit@debbugs.gnu.org id=B20629.14329296853500 (code B ref 20629); Fri, 29 May 2015 20:02:02 +0000 Original-Received: (at 20629) by debbugs.gnu.org; 29 May 2015 20:01:25 +0000 Original-Received: from localhost ([127.0.0.1]:60880 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YyQT5-0000uN-Tk for submit@debbugs.gnu.org; Fri, 29 May 2015 16:01:24 -0400 Original-Received: from mail-wg0-f41.google.com ([74.125.82.41]:36592) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YyQT3-0000u9-0y for 20629@debbugs.gnu.org; Fri, 29 May 2015 16:01:21 -0400 Original-Received: by wgbgq6 with SMTP id gq6so71394679wgb.3 for <20629@debbugs.gnu.org>; Fri, 29 May 2015 13:01:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=UQVDtZSmsl/JuDl5j+Cw9b+OgWgGgP/mRJhg51HlCCo=; b=HpUmCjDqxVfucfX6seVX/1PJL0APdxZG1Qg06BkyuD67YHOB335URp6HWbumI/ey8/ q+swk/zGVACgaLzEsi6LiXnVL/bEWSzGR7SFZFBiy4Sd4oJbQpS6P4WRjkjRZOWqZfz4 34oIJVTKqjS83Hrd/uug04VxbTTqj3rcJt46EhQ2Tc3gW0rchHcX11QmEDDZTOosG+YG bKuYkuPRoP84MqLtXQhekmBPiZX3kfTMz+JqBaSu4iI0Az4CC+3r2zPpPNV+1K70luXu hFubf3GmPTC6DYAqqxRTgf2OmXkFjsLwYIBlP1pCLc4jJXCSU7VlZ/BuuYYm26o3I3DF prbw== X-Received: by 10.180.91.40 with SMTP id cb8mr9615900wib.64.1432929675226; Fri, 29 May 2015 13:01:15 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id ei8sm9754183wjd.32.2015.05.29.13.01.14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 May 2015 13:01:15 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <83617bw84o.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:103331 Archived-At: On 05/29/2015 09:28 PM, Eli Zaretskii wrote: > Compatibility aside, I think what most users will want should be the > default. What Exuberant ctags does now might not yet reflect the > changes in Emacs, from etags.el's UI to xfer. Once they learn about > that, they might turn that flag on by default as well. There's nothing particularly xref-specific in using the one or the other approach. xref output buffer doesn't display the tag names, only patterns (although printing the tag names as well can be added). > For moderate-size projects, the obarray-based completion is > instantaneous, Yes. I explicitly didn't mention it. Only the time to build the obarray the first time, as well as non-obarray based completion. You might be better positioned to judge whether these are serious. > I don't think we can safely do that, since different characters can > appear in identifiers of different languages. By using the qualifier > string that is natural for the language, we make sure we never get > conflicts with the identifiers themselves. The name segments could be escaped WRT those two characters. > Also, these qualified tags are for human consumption, which is another > argument on favor of language-specific syntax. Sure, it's a good argument. > Which means C++ programmers will probably be confused by them. They are not hard to learn. IMO, "::" is a bad separator for method qualifier, since the same operator is used for namespace resolution.