From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#67687: Feature request: automatic tags management Date: Thu, 21 Dec 2023 02:24:01 +0200 Message-ID: <812729c8-726f-d60e-2603-2d8e588929fd@gutov.dev> References: <2f86b882-9ec1-f63f-d90b-5f8f7ae114f2@gutov.dev> <58D84A29-9A63-45BA-AD8B-B476CDC931A1@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11602"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: 67687@debbugs.gnu.org To: Jon Eskin , Eli Zaretskii , Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Dec 21 01:25:21 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1rG6sK-0002qF-FS for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 21 Dec 2023 01:25:21 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rG6s0-0005sn-OM; Wed, 20 Dec 2023 19:25:00 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rG6rz-0005sf-98 for bug-gnu-emacs@gnu.org; Wed, 20 Dec 2023 19:24:59 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rG6rz-0001Hk-17 for bug-gnu-emacs@gnu.org; Wed, 20 Dec 2023 19:24:59 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rG6s2-0004GS-01 for bug-gnu-emacs@gnu.org; Wed, 20 Dec 2023 19:25:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 21 Dec 2023 00:25:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 67687 X-GNU-PR-Package: emacs Original-Received: via spool by 67687-submit@debbugs.gnu.org id=B67687.170311825616329 (code B ref 67687); Thu, 21 Dec 2023 00:25:01 +0000 Original-Received: (at 67687) by debbugs.gnu.org; 21 Dec 2023 00:24:16 +0000 Original-Received: from localhost ([127.0.0.1]:42088 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rG6rH-0004FI-On for submit@debbugs.gnu.org; Wed, 20 Dec 2023 19:24:16 -0500 Original-Received: from out2-smtp.messagingengine.com ([66.111.4.26]:60765) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rG6rF-0004F5-PS for 67687@debbugs.gnu.org; Wed, 20 Dec 2023 19:24:14 -0500 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1B01B5C072A; Wed, 20 Dec 2023 19:24:05 -0500 (EST) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 20 Dec 2023 19:24:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1703118245; x=1703204645; bh=rSOE84PTNwr8XSQzvvKZ3Ps1W8VUu78iAEFuT8qJ8J8=; b= LXLFntbABAMFyn7I+UJxse3x/nmN8ZzbpDgOjXtue5CKXilwF4gsdbxLYRztT9/6 V5mxi2DitQLU3l8HAxYZRg/coKuY9+EQRG6507gsLlPOqTxCyMzxDkQ/CTZoFDjG S5yZB4uXI4EEjqvKUDlNibmx4DhIgxAjnndThU+X6ezzuLwXKtnjQpvcX2z3Qz7q tP3bUNthlN2HEKBOmwIq0PRis3CvOQArI7q/zcdMBe5Rs//y8FTis2JlYfuj3cZe fJCXpe5/qGm16Au0T+zeoVZ6G40R660BsRwAxOdz7rM0In4bPox7qA0gUvITyEzx Hh9vtEViuDP5GhvRcDVZag== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1703118245; x= 1703204645; bh=rSOE84PTNwr8XSQzvvKZ3Ps1W8VUu78iAEFuT8qJ8J8=; b=f W1+NNmL35dnPbU3+m2NPQhQRwK2EgtKByhHhQBT5BdweELzxTkbLevGmPXfAVDNt fiqgnS0K+Nd5IxSAWVOTUOt94tE7ff+umFQcqgz3PfUNS3OkH5lelfpLS3NYI92Y CYR+DYl4m25vcRe3rngAM7r4n+EpqGVnydFejRLfkeCF5bD6VIZwBbLpzN3v3wU0 CurNVftIWPOP8wmpUN55NRl46QIEE1sy2Tasz45RxOhn94LevdEnE8HP3wWZmAGG UT2Ip9iT++DqTbMH1Ps4/73MdxMNDdj2vV5Q0srzkGOizVVyrF3Y+zvlazknrDTQ LCR+n7X5IzijqOC9VRHRw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvddufedgvdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhephfffheeljeffgeffueeghfekkedtfffgheejvdegjeettdduheeufffggfef jeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepug hmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 20 Dec 2023 19:24:03 -0500 (EST) Content-Language: en-US In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:276604 Archived-At: On 20/12/2023 23:11, Jon Eskin wrote: > >> Wow! This is excellent, worked like a charm on my end. >> >> I’m going to get this set up on a few different machines and take some >> time to build feedback. >> >> Thank you! > > Just a quick follow up - I’ve been using this every day. I’ve been able > to work without thinking about tags at all, and it’s been a huge QOL > upgrade for me. Excellent. > The only road-bumps I had in the last few weeks were the following: > > 1) In some repositories I unknowingly had an existing universal ctags > file “tags”. When I did, trying to goto-def would give an error like > "user-error: File /Users/jon/development/c/clp/TAGS is not a valid tags > table”. This was misleading, because the actual file on my filesystem is > "/Users/jon/development/c/clp/tags”. Usually I differentiate ctags > format from etags by the capitalization of the filename, and that error > message makes it look like it’s an etags file. I’m guessing this has > something to do with MacOS file system case insensitivity on the file > system. Hm, the first advice I would give is customize 'etags-regen-tags-file' to something else -- e.g. "RETAGS"? Then it won't match existing files. Later we could also add some file format verification (a regexp search or two), but probably not in the first version. > 2) I had always generated tags with a path argument for some reason, so > when I customized “Etags Regen Program” to “ctags -e -R .”, I got an > error since it appends an -o option to the end. I just needed to glance > at the source and experiment for a minute to realize I just needed to > remove the “.”. And "-R", I hope. Though it probably makes no difference, since none of the arguments passed to it are directories. Yeah, "-R ." is antithetical to how the program is used. We can extend the :type argument for this option, adding "ctags -e" at least. Maybe a longer docstring as well. > I don’t mean to suggest those are problems to be fixed, I can’t really > think of any addition or change that would make sense to try to address > them, but I figured I would report them in case you had any ideas. > > Overall this package gets a big thumbs up from me and I think it would > be a great inclusion in a future release. Thank you for sharing it! Thanks for testing! That is a good sign (with another positive bit of feedback on Reddit yesterday), so I think it's time to ask the head maintainers what they think about the inclusion of this feature in the core now. Eli/Stefan?