From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Generation of tags for the current project on the fly Date: Wed, 17 Jan 2018 22:12:21 +0200 Message-ID: <834lnkw8gq.fsf@gnu.org> References: <4559858d-eb32-d071-fdad-e51430700260@yandex.ru> <83shbb30z1.fsf@gnu.org> <8360863o6a.fsf@gnu.org> <27a58fb2-d2ee-e5fc-158d-ec41be401987@yandex.ru> <83y3l0za1f.fsf@gnu.org> <259c557d-e3a3-c01b-9ba3-30df09d247ea@yandex.ru> <83inc3znpu.fsf@gnu.org> <98f4f0c3-6815-bf86-fa23-1a330c60b9f3@yandex.ru> <83d129y9oq.fsf@gnu.org> <4a91acc7-78f9-600f-2fa4-1bed70b107e2@yandex.ru> <83k1wgwl1i.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1516219850 4103 195.159.176.226 (17 Jan 2018 20:10:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 17 Jan 2018 20:10:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 17 21:10:45 2018 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 1ebu2i-0000Wc-Gu for ged-emacs-devel@m.gmane.org; Wed, 17 Jan 2018 21:10:40 +0100 Original-Received: from localhost ([::1]:59252 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ebu4i-00042e-Db for ged-emacs-devel@m.gmane.org; Wed, 17 Jan 2018 15:12:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37145) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ebu4b-00042P-Ji for emacs-devel@gnu.org; Wed, 17 Jan 2018 15:12:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ebu4X-0002mj-Gm for emacs-devel@gnu.org; Wed, 17 Jan 2018 15:12:37 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42032) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ebu4X-0002md-DD; Wed, 17 Jan 2018 15:12:33 -0500 Original-Received: from [176.228.60.248] (port=2958 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ebu4V-0005F2-Po; Wed, 17 Jan 2018 15:12:33 -0500 In-reply-to: (message from Dmitry Gutov on Wed, 17 Jan 2018 22:43:17 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:222055 Archived-At: > Cc: emacs-devel@gnu.org > From: Dmitry Gutov > Date: Wed, 17 Jan 2018 22:43:17 +0300 > > On 1/17/18 18:40, Eli Zaretskii wrote: > > >> The information is inside the TAGS file, isn't it? > > > > Not really: the signature of each file at the moment of scan is > > missing, and maybe also other things. > > Meaning it's not known at etags runtime? That's true. It's also not recorded after the run, so that the next run could compare against it. > Make tracks which files need to be recompiled, right? This could reuse > the same mechanism, if possible. Make doesn't support incremental builds, except on file granularity. Doing that with etags would be easy, but you say that is not the "incremental" tagging you had in mind, you want the granularity to be below file, i.e. on tag level. For that, a single time stamp of the TAGS file is insufficient, because all it can tell you is which files need to be re-tagged, whereas you want to know that on a per-tag basis.