From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#65520: 30.0.50; [FR Xref] Project-wide operations Date: Sat, 26 Aug 2023 07:31:05 +0200 Message-ID: References: <5fc3aec1-019e-49c8-d939-91042f16650b@gutov.dev> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="352"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 65520@debbugs.gnu.org, Visuwesh To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Aug 26 07:32:09 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 1qZlu5-000ATz-7Q for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 26 Aug 2023 07:32:09 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qZltv-0004JA-78; Sat, 26 Aug 2023 01:31:59 -0400 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 1qZltt-00046u-7q for bug-gnu-emacs@gnu.org; Sat, 26 Aug 2023 01:31:57 -0400 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 1qZlts-0004RL-Vc for bug-gnu-emacs@gnu.org; Sat, 26 Aug 2023 01:31:56 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qZltx-0008Vf-UA for bug-gnu-emacs@gnu.org; Sat, 26 Aug 2023 01:32:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 26 Aug 2023 05:32:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65520 X-GNU-PR-Package: emacs Original-Received: via spool by 65520-submit@debbugs.gnu.org id=B65520.169302788432643 (code B ref 65520); Sat, 26 Aug 2023 05:32:01 +0000 Original-Received: (at 65520) by debbugs.gnu.org; 26 Aug 2023 05:31:24 +0000 Original-Received: from localhost ([127.0.0.1]:41500 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qZltL-0008UQ-K3 for submit@debbugs.gnu.org; Sat, 26 Aug 2023 01:31:23 -0400 Original-Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]:51432) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qZltF-0008U3-S1 for 65520@debbugs.gnu.org; Sat, 26 Aug 2023 01:31:21 -0400 Original-Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-99bcc0adab4so197495766b.2 for <65520@debbugs.gnu.org>; Fri, 25 Aug 2023 22:31:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693027867; x=1693632667; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=uH1wpva8qc+hAjQWT4ivbt75fIOEHNHrsDofiywdf1Q=; b=DOmTU1vgVELaOFmkqLg8OcG/+6uQ1bUtyfDTbazD3LD/8GfhcxDRFl4P2Wbm/4rCh4 mR+FNzPe6kZFL2YdpaHNPkPxlMnob8B79jP9vomcixZrvXaVCT/EG4T+MxJoGfedG07q q32L68pHLBbvaQZYmZjk9gBh9MGpaSGe/grzPjA1ZygNk5py+MyEAJq/jL0pbYc+J8bd I92rC+M5CGHMiFF0YUMF+0hZo346Ouzz1rKfJQi+be3KLd9k1bFDI8x/6wnlwAQrXRjq XlrtRHUqSXHq6/NPX4aNUi1tD+ZTlU1inOSgw+1gV1TY8yDFb8iVqKMJt61T5mam7kcV nlVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693027867; x=1693632667; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=uH1wpva8qc+hAjQWT4ivbt75fIOEHNHrsDofiywdf1Q=; b=De8UKNmyE/uqjivg8+bbLBz+FZaiRX1OkJ5ARncLKew6Czu5JHsu87ZaKb33mCiSIK rFWTe0zVWv7J0DownfW8nfOiRCObYSCxs4F1siLQyYjVaHCEdlD7rpr4vOAFiiS0BJBG DXSqzMaliIpp84A8zjyXoFXkPL/S4Y0ctNPg+1/9JGGNDHImv8hq0Lza1JnKaOIFTqkE TOpCGbiWIQxe0rVK36AMksOufF0O51s68xNGcmR8gVUNtU5NBPPsK82YXF0iuM+IgXop E+dP8qxaThnqeyhlE5573T7aoxo72KFAEZHB3EkL77OewW4Hw25x5Y6sgmXLevLVieUF yqew== X-Gm-Message-State: AOJu0YwkD4C1+5245Q12Vd59+3h9lAIBkELEQfy4pZ2FUFz8fHUzu9y/ fAcze1M+Ox0kjywHKQYQMDIQS1Ex3i8= X-Google-Smtp-Source: AGHT+IEs2g9zMeUFh8CazMDSq1ByJKu/hyvlRqLrNadvMyv0e2+eayVyVuP9F5myTqBClnLt5871Qw== X-Received: by 2002:a17:906:5385:b0:99c:55c0:ad15 with SMTP id g5-20020a170906538500b0099c55c0ad15mr15659467ejo.38.1693027866721; Fri, 25 Aug 2023 22:31:06 -0700 (PDT) Original-Received: from Mini.fritz.box (pd9e36ea3.dip0.t-ipconnect.de. [217.227.110.163]) by smtp.gmail.com with ESMTPSA id q22-20020a170906361600b0099cadcf13cesm1688162ejb.66.2023.08.25.22.31.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Aug 2023 22:31:06 -0700 (PDT) In-Reply-To: <5fc3aec1-019e-49c8-d939-91042f16650b@gutov.dev> (Dmitry Gutov's message of "Fri, 25 Aug 2023 19:20:03 +0300") 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:268465 Archived-At: Dmitry Gutov writes: > On 25/08/2023 10:03, Gerd M=C3=B6llmann wrote: >> Dmitry Gutov writes: >>=20 >>>> In C mode, Xref works using Eglot, in ELisp mode it uses something >>>> else >>>> (I have no tags tables). Both work really well, but I apparently have >>>> to be in an ELisp buffer to use one and in a C buffer to use the other. >>>> Feature request: Is it possible to use more than one backend at the >>>> same >>>> time? So that I could C-M-. to find an ELisp function while being in a >>>> C file? I couldn't find something like that mentioned in the docs, so= I >>>> guess it's not yet possible. >>> >>> No such capability at the moment, but we indeed have an ELPA package >>> xref-union which implements the "merging" feature that has been >>> requested in the past. >> Thanks also to Visuwesh for pointing me to xref-union. > > Have you tried it? Not yet. I'm still hoping someone else (tm) builds something, so that I don't have to do anything. > By setting up both it and the > xref-backend-functions manually (in a hook) in every relevant buffer > you might get more or less the requested behavior. If not, what does > feel unsatisfying still? > >>> A naive approach, or for the new code to search across different open >>> buffers and look for different available xref-backend-functions >>> elements. And then prompt the user, and then call (?) the said >>> function in one of the buffers it was found in, because in all >>> likelihood it would fail in unrelated ones. >>> >>> Perhaps the solution is to add a new facility to Xref, where different >>> "projects" would be able to register globally in. A feature request >>> indeed. >> I'm not sure about the "different project in the same session" >> thing. >> My mental model is like so: I'm in a Git repo (Emacs), which is, I >> think >> also a project in the project.el sense. This project contains differnt >> sets of files for which information is available using different >> backends (Eglot, Etags, others depending on the kind of project). What >> U'd like to have is something on the level of such a project, if you >> know what mean. That is, M-. would take all available info for such a >> project into account. > > Indeed, it's also a question of mental model, which we might have > different. When I was saying "different projects" and "register > globally", I was thinking of being able to jump to Emacs' sources and > hack them from anywhere: from any other project I might be working on > at the moment. > > If we're talking about Emacs development only, a "combined" backend > might make more sense (see the other email). No, I didn't mean Emacs development specifically, although that's probably the only things I'd use such a facility for. The whole thing would be like in some IDEs, with their "usual" idea of project. I'm not 100% sure, but I think I've seen vscode being used with different languages (JS, CSS, Java...) and offering such project-wide stuff.