From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Etags.el (was: UI inconveniences with M-.) Date: Wed, 29 Apr 2015 18:52:32 +0300 Message-ID: <83sibjszi7.fsf@gnu.org> References: <83zja6b3tc.fsf@gnu.org> <54A24079.4020902@yandex.ru> <54A2FF47.6010207@yandex.ru> <54A86135.7080004@yandex.ru> <54A90002.7080009@gmx.at> <54A9C3FB.7000602@yandex.ru> <54AA3881.3080304@gmx.at> <54ABBB47.7010603@yandex.ru> <837fszx7iy.fsf@gnu.org> <83pp6pwqnw.fsf@gnu.org> <553EB74A.4030208@yandex.ru> <83618gwbb1.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1430322778 32089 80.91.229.3 (29 Apr 2015 15:52:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Apr 2015 15:52:58 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 29 17:52:52 2015 Return-path: Envelope-to: ged-emacs-devel@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 1YnUI5-00044q-Mz for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 17:52:49 +0200 Original-Received: from localhost ([::1]:39795 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnUI4-00083w-V2 for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 11:52:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46067) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnUHy-0007wo-Cv for emacs-devel@gnu.org; Wed, 29 Apr 2015 11:52:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnUHt-00085s-2G for emacs-devel@gnu.org; Wed, 29 Apr 2015 11:52:42 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:54642) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnUHs-00085D-RN for emacs-devel@gnu.org; Wed, 29 Apr 2015 11:52:37 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NNK00E00RWAXF00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Wed, 29 Apr 2015 18:52:35 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NNK00E5JS3NXH10@a-mtaout22.012.net.il>; Wed, 29 Apr 2015 18:52:35 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:186022 Archived-At: > From: Stefan Monnier > Cc: emacs-devel@gnu.org > Date: Tue, 28 Apr 2015 23:12:53 -0400 > > >> I really think the etags backend should only return data when the TAGS > >> file is in one of the parents of the current directory. > > That goes back to the "working on several projects" discussion of > > yore. Specifically, you might be working on two related packages > > (e.g., one calls the other) that live in two different directories. > > And as mentioned back then, this would be solved by providing a way for > the user to tell etags.el about the link between those two projects. > For the case where this link only exists during the running session, we > could simply use the existing "visit-tags-table" functionality where you > can add a TAGS file to the one(s) already loaded, so the new > functionality would behave similarly to the old one. And as mentioned back then, until something like this is coded, this discussion is just theoretical. > >> And it should also be able to keep several independent TAGS tables > >> opened for different projects in different directory trees. > > It already does that. > > > No it doesn't. It lets you use the union of a set of TAGS tables, which > means that the TAGS tables of independent projects pollute each other. It's an approximation, yes. Feel free to implement something better; until then, what we have is quite good IME (I use it every day).