unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Donovan via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 63651@debbugs.gnu.org
Subject: bug#63651: possible eglot xref-find-references optimization
Date: Tue, 4 Jul 2023 09:55:57 -0400	[thread overview]
Message-ID: <CAPVWWDVZBOT7zddtgksGUsZgX1T_ALDrxeNixePJY4bmUVjw4A@mail.gmail.com> (raw)
In-Reply-To: <CAPVWWDUqoJWUEF9-2ziMiTtFdA_EqV07ME-uSjGv+GWp=cgO0Q@mail.gmail.com>

Any progress? Were you able to observe the problem?

cheers
alan

On Wed, 24 May 2023 at 17:22, Alan Donovan <adonovan@google.com> wrote:
>
> On Wed, 24 May 2023 at 12:29, João Távora <joaotavora@gmail.com> wrote:
> > Thanks for reporting this Alan, it is an interesting point. (Next time you can add me on CC directly so that i don't miss the message in this list, which i don't always track closely)
>
> Will do.
>
> > Could you provide a test case where these ~= 1300 xref matches are produced? I suppose it is some Go repository? With a standard gopls? But which file/position and which command should one use?
>
> $ git clone https://github.com/golang/tools
> $ cd tools
> $ (cd gopls && go install)   # if you don't have it already
> $ emacs gopls/internal/lsp/cache/analysis.go
> Then search for fmt.Sprintf (e.g. on L246) and do xref-find-references
> on it. I get about 1300 matches.
>
> cheers
> alan





      reply	other threads:[~2023-07-04 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPVWWDXj+au=50v00jK7DNGFX33p7uyz_x+iQMGxk6Gu2p5saA@mail.gmail.com>
2023-05-22 17:45 ` bug#63651: possible eglot xref-find-references optimization Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-24 16:28   ` João Távora
2023-05-24 21:22     ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 13:55       ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPVWWDVZBOT7zddtgksGUsZgX1T_ALDrxeNixePJY4bmUVjw4A@mail.gmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63651@debbugs.gnu.org \
    --cc=adonovan@google.com \
    --cc=joaotavora@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).