From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Xref/tags/lsp possible bug Date: Mon, 25 Apr 2022 17:48:08 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8606"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: help-gnu-emacs@gnu.org To: Dmitry Gutov Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Apr 25 23:48:53 2022 Return-path: Envelope-to: geh-help-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 1nj6Zh-0001ys-0s for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 25 Apr 2022 23:48:53 +0200 Original-Received: from localhost ([::1]:45766 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nj6Zf-0004kE-2r for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 25 Apr 2022 17:48:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56552) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nj6ZB-0004k4-VJ for help-gnu-emacs@gnu.org; Mon, 25 Apr 2022 17:48:22 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:1700) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nj6Z9-0000SJ-3n for help-gnu-emacs@gnu.org; Mon, 25 Apr 2022 17:48:20 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 89D75802D3; Mon, 25 Apr 2022 17:48:16 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 122B78026A; Mon, 25 Apr 2022 17:48:15 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1650923295; bh=tb1qDII7DPK/SSJK8MraDmFAOPTdeYqVYB8jPG9pjPA=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=kZUHzBvyLVwFuSQ4cSZzQAtpptWnC4YAUoa9v3E6JHKzxwPF8OeszrG6xlQPQv8MF LJMxfk37XnerjJFwB59thORXskGmbTAwVX9YDk6gtqkZaJgsdZrDV1w8/lJG+CLWzR qEPQJOYOM2MASQ4KIh/sA40ciiZnShhPCF10r0VaggbDZGEdIVcGgODOTC4408Cn2M x31TyJ+A9GxxyERDEoD8nJQIosViPDRA+5M0GjiYV9D7Rku3AmGHVj9lCrvJlne9G7 CMTNuPoGOCAr/N2FitIITVNkKjHvpPPZ4pglpr+mQXyBEix///UBYm1TtDDH76O2A1 Q+rW0uNsXh4zw== Original-Received: from alfajor (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 798D512026E; Mon, 25 Apr 2022 17:48:14 -0400 (EDT) In-Reply-To: (Dmitry Gutov's message of "Mon, 25 Apr 2022 23:29:02 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:137023 Archived-At: > 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