From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Automatic (e)tags generation and incremental updates Date: Tue, 12 Jan 2021 19:15:21 +0200 Message-ID: <8335z6dql2.fsf@gnu.org> References: <779a6328-9ca5-202a-25a2-b270c66fe6dd@yandex.ru> <8fc5e96c-ebb8-c668-9b2a-c7c4ee54c0b9@yandex.ru> <83r1mwltob.fsf@gnu.org> <0bee9ab4-46bc-b6fd-97b6-e26cc80f1610@yandex.ru> <875z45dbm7.fsf@tromey.com> <1e9c9572-52ee-339b-78a2-731b9eb5f3de@yandex.ru> <871resd93f.fsf@tromey.com> <83mtxffrou.fsf@gnu.org> <106abdbb-ce7a-4911-0831-149da3dccfb3@yandex.ru> <83o8hudwgo.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10902"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, tom@tromey.com, emacs-devel@gnu.org, john@yates-sheets.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 12 18:38:43 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kzNcx-0002ja-M9 for ged-emacs-devel@m.gmane-mx.org; Tue, 12 Jan 2021 18:38:43 +0100 Original-Received: from localhost ([::1]:48246 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kzNcw-00059j-GI for ged-emacs-devel@m.gmane-mx.org; Tue, 12 Jan 2021 12:38:42 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35470) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kzNGH-0003mH-25 for emacs-devel@gnu.org; Tue, 12 Jan 2021 12:15:20 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35643) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kzNGG-0004yU-6W; Tue, 12 Jan 2021 12:15:16 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2023 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kzNG7-0005rs-Ke; Tue, 12 Jan 2021 12:15:08 -0500 In-Reply-To: (message from Dmitry Gutov on Tue, 12 Jan 2021 18:48:24 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:263008 Archived-At: > Cc: tom@tromey.com, john@yates-sheets.org, philipk@posteo.net, > emacs-devel@gnu.org > From: Dmitry Gutov > Date: Tue, 12 Jan 2021 18:48:24 +0200 > > (insert-file-contents "...") takes 0.15 in this example, which would > make it possible to use if etags implemented the same logic that we do > in Elisp currently Which logic is that? what does it do? > > Anyway, TAGS and etags.el were designed to be very tolerant to > > changes, so you shouldn't need to update very often. > > I want it to update reliably; maybe not too often (depending on a > project), but if a user switches to a different Git branch, they should > be confident that they'll see the changes reflected in the index soon. > Even (and especially) if those are big changes. What about regenerating etags only if M-. etc. fail to find an identifier? > Right now only the update-on-save feature is in there, but I have to > tell you, having a newly written function in the index right away > (without having to invoke any commands or switch to the terminal) is > pretty nice. Of course, but then the user will need to be prepared to pay the price. TANSTAAFL.