unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Xref/tags/lsp possible bug
Date: Sat, 23 Apr 2022 15:52:18 +0300	[thread overview]
Message-ID: <83v8v0nerh.fsf@gnu.org> (raw)
In-Reply-To: <CAJczNmAGo5B1bxf2JCaQJTi5fJ07BoBWobDOh8daLHaCWuofog@mail.gmail.com> (message from Alessandro Bertulli on Sat, 23 Apr 2022 14:17:03 +0200)

> From: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
> Date: Sat, 23 Apr 2022 14:17:03 +0200
> 
> - First, when using LSP modes (both lsp-mode and eglot), the command
>   xref-find-definitions only acts on the symbol under point. I
>   explain: usually, in vanilla Emacs (emacs -q) if point is on a
>   whitespace/not on a symbol, invoking the command (bound to M-.) will
>   prompt you for an identifier to search for. However, when LSP is
>   active, it directly searches for an empty symbol, for example
>   reporting something similar to: "Symbol  not found" (not the double
>   space, which makes me think it searches for a symbol named ""). As I
>   said, this happend both for lsp-mode and eglot, so maybe is a
> problem of xref?
> 
> - Second, and minor: while I was investigating, I noticed that,
>   depending on the loaded packages, when giving M-., xref sometimes
>   asks for the symbol to search, sometimes it asks the TAGS table
> first. What package can be the problem?
> 
> Do you think it is a bug of Emacs? Do you know a way to resolve?
> Thanks to all!

Every major mode needs to set up its Xref support.  It sounds to me
that what you experience are the differences in the major modes you
use in each case.



  reply	other threads:[~2022-04-23 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 12:17 Xref/tags/lsp possible bug Alessandro Bertulli
2022-04-23 12:52 ` Eli Zaretskii [this message]
2022-04-24 23:06   ` Dmitry Gutov
2022-04-25  1:32 ` Dmitry Gutov
  -- strict thread matches above, loose matches on Subject: below --
2022-04-23 15:28 Alessandro Bertulli
2022-04-25 10:01 Alessandro Bertulli
2022-04-25 20:05 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-04-25 20:29   ` Dmitry Gutov
2022-04-25 21:48     ` Stefan Monnier
2022-04-26  1:41       ` Dmitry Gutov

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=83v8v0nerh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).