unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Xref/tags/lsp possible bug
Date: Mon, 25 Apr 2022 17:48:08 -0400	[thread overview]
Message-ID: <jwv8rrs25z7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <e5ef89a7-490e-d5de-7e91-eff6bac06fa5@yandex.ru> (Dmitry Gutov's message of "Mon, 25 Apr 2022 23:29:02 +0300")

> As for the reason why: my guess is that the protocol was designed as
> a common ground for a number of existing code assistance libraries/tools
> already developed within Microsoft, rather than something from a blank
> slate, and those are inevitably biased toward a particular UI.

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.

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.


        Stefan




  reply	other threads:[~2022-04-25 21:48 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 [this message]
2022-04-26  1:41       ` Dmitry Gutov
  -- 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=jwv8rrs25z7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dgutov@yandex.ru \
    --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).