unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Xref/tags/lsp possible bug
Date: Tue, 26 Apr 2022 04:41:15 +0300	[thread overview]
Message-ID: <2be64dba-a131-58aa-bbe2-6c66fe15a3eb@yandex.ru> (raw)
In-Reply-To: <jwv8rrs25z7.fsf-monnier+emacs@gnu.org>

On 26.04.2022 00:48, Stefan Monnier wrote:
> Indeed, the protocol has a fairly strong "ad-hoc" feel to it.
> It doesn't cleanly separate the UI from the rest.  For example, a lot of
> presentation choices are actually made in the server rather than in
> the client.

Yep.

> It's also reflected in the name of requests like "hover" which
> fundamentally asks for information related to some position in the code,
> but encodes the idea that this information will be presented as popup
> boxes as the mouse "hovers" over that location.

...and doesn't otherwise describe what that data should contain.



  reply	other threads:[~2022-04-26  1:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 10:01 Xref/tags/lsp possible bug 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-23 15:28 Alessandro Bertulli
2022-04-23 12:17 Alessandro Bertulli
2022-04-23 12:52 ` Eli Zaretskii
2022-04-24 23:06   ` Dmitry Gutov
2022-04-25  1:32 ` 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=2be64dba-a131-58aa-bbe2-6c66fe15a3eb@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).