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:55:56 +0200 Message-ID: <83y2gyca4z.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> <8335z6dql2.fsf@gnu.org> <3c688f2e-a32c-63b8-235b-8ef92e87fe83@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17107"; 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:57:17 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 1kzNuv-0004L2-8y for ged-emacs-devel@m.gmane-mx.org; Tue, 12 Jan 2021 18:57:17 +0100 Original-Received: from localhost ([::1]:42290 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kzNuu-0001lQ-9l for ged-emacs-devel@m.gmane-mx.org; Tue, 12 Jan 2021 12:57:16 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45528) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kzNtQ-0000i7-H4 for emacs-devel@gnu.org; Tue, 12 Jan 2021 12:55:44 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36552) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kzNtP-0002Y8-47; Tue, 12 Jan 2021 12:55:43 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4740 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kzNtN-00084p-OS; Tue, 12 Jan 2021 12:55:42 -0500 In-Reply-To: <3c688f2e-a32c-63b8-235b-8ef92e87fe83@yandex.ru> (message from Dmitry Gutov on Tue, 12 Jan 2021 19:32:18 +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:263010 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 19:32:18 +0200 > > > What about regenerating etags only if M-. etc. fail to find an > > identifier? > > There are downsides. > > You will have to press M-. twice sometimes with that approach. Why twice? I thought about regenerating automatically once the search fails, then retrying the search with an updated tags table. > Completion will routinely fail to show some tags that should be present. > Also, if the rescan takes a while, I'm not sure you'd want to do that on > every 'M-.' failure. You could also regenerate when the user switches to another branch. That's not a very frequent thing to do.