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: Adding support for xref jumping to headers/interfaces Date: Thu, 09 Mar 2023 19:31:23 +0200 Message-ID: <83ilf925n8.fsf@gnu.org> References: <83bklin83z.fsf@gnu.org> <865ybmu2ha.fsf@stephe-leake.org> <39e25c9a-b4cc-a0ce-3f2a-1d2a1fc243d0@yandex.ru> <83pm9sfxfa.fsf@gnu.org> <861qm4tkih.fsf@stephe-leake.org> <71ea5e83-183f-2ae3-8146-6a31045a0309@yandex.ru> <834jqzafse.fsf@gnu.org> <83h6uv47e8.fsf@gnu.org> <4639d7ca-2109-864c-33c0-38e65f26f262@yandex.ru> <835ybb3txt.fsf@gnu.org> <83wn3q311i.fsf@gnu.org> <412afa2d-5dbc-52da-39c4-99be3873929c@yandex.ru> <83o7p20wdi.fsf@gnu.org> <72b09256-5a1b-8962-9e3c-7d2ffd0dc0d7@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32854"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stephen_leake@stephe-leake.org, john@yates-sheets.org, rms@gnu.org, fgunbin@fastmail.fm, casouri@gmail.com, sbaugh@janestreet.com, emacs-devel@gnu.org, azeng@janestreet.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 09 18:32:16 2023 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 1paK7j-0008L3-Bx for ged-emacs-devel@m.gmane-mx.org; Thu, 09 Mar 2023 18:32:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1paK7E-0008H5-Fq; Thu, 09 Mar 2023 12:31:44 -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 1paK7C-0008Gj-MD for emacs-devel@gnu.org; Thu, 09 Mar 2023 12:31:43 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1paK7B-0007N0-LR; Thu, 09 Mar 2023 12:31:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=uOCxrG5ig4Use9rPQvxYzvL5SwVmBgct0f+ijW1taew=; b=gIsgR9mA8wta hqxOry7lh+V0OrAK0S/T6YJyrgviBx6KkrqTIM/TcUF996VCtv20Rnj1sHvENyRuV1FR0Z8+23L8h XgILC1VMMUXxMQ/QquBqX2PeUW0jE6SCRAwJrqRyDgVYySvQEIzigGd7Q8oErIwbWd08AekVjmD7U u1dlXbhUrmI6bAiPBINx8vC8KEN6hzWEBy2gKehL2GpdHJco27uA00UVMLM8ASHO8AIPblpqdCul/ 4hLPFxqkXt4cAaiGladTNXzKf4Xa/AtaKwZ0nAA4u3R6y2UElff8MrZQBLjVfgnSn2kSygwmn5UsE Z6ci7AfCtyHrJe3NSOCuqw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1paK75-0007Tp-GD; Thu, 09 Mar 2023 12:31:35 -0500 In-Reply-To: <72b09256-5a1b-8962-9e3c-7d2ffd0dc0d7@yandex.ru> (message from Dmitry Gutov on Thu, 9 Mar 2023 18:53:42 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304218 Archived-At: > Date: Thu, 9 Mar 2023 18:53:42 +0200 > Cc: stephen_leake@stephe-leake.org, john@yates-sheets.org, rms@gnu.org, > fgunbin@fastmail.fm, casouri@gmail.com, sbaugh@janestreet.com, > emacs-devel@gnu.org, azeng@janestreet.com > From: Dmitry Gutov > > There is also the issue of having those files generated and saved to > appropriate files. If I run 'etags -o TAGS', I might not expect that > additional files will appear. Or existing ones -- overwritten. That's not what I had in mind. I thought we'd run etags several times, as in etags --enums-only -o TAGS.enum etags --decls-only -o TAGS.decl etc. > > OTOH, having those in a single file will need Xref to cope with > > multiple matches, something that currently we largely avoid. You'd > > have the same symbol mentioned once for declaration, another time for > > definition, perhaps yet another time for interface, etc. > > We already support duplicates, don't we? Only when there's no way around that, and we consider that unfortunate when it does happen.