From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jostein_Kj=c3=b8nigsen?= Newsgroups: gmane.emacs.devel Subject: Re: Elisp LSP Server Date: Mon, 25 Oct 2021 07:46:59 +0200 Message-ID: <38722f6d-3406-ce6c-43ae-7d322d597e59@secure.kjonigsen.net> References: <16338bdc2497fc51c6fb6d54ab370bfb@webmail.orcon.net.nz> <87ee99dv34.fsf@gmail.com> <07cf50ddddb5a9556aa94201a7ac88c9@webmail.orcon.net.nz> <87r1d0562u.fsf@yahoo.com> <87r1cz7qcd.fsf@posteo.net> <87bl4367av.fsf@yahoo.com> Reply-To: jostein@kjonigsen.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------cXxlECEeMsE8dMHtVTMErxTQ" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29319"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 25 07:51:14 2021 Return-path: Envelope-to: ged-emacs-devel@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 1mest5-0007MH-KL for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Oct 2021 07:51:13 +0200 Original-Received: from localhost ([::1]:56340 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mest0-0007CC-HC for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Oct 2021 01:51:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56380) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mespC-0006TS-IM for emacs-devel@gnu.org; Mon, 25 Oct 2021 01:47:11 -0400 Original-Received: from wout1-smtp.messagingengine.com ([64.147.123.24]:36225) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mesp9-0001QA-EU for emacs-devel@gnu.org; Mon, 25 Oct 2021 01:47:09 -0400 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 2DF313201D69 for ; Mon, 25 Oct 2021 01:47:03 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 25 Oct 2021 01:47:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= secure.kjonigsen.net; h=content-type:message-id:date :mime-version:reply-to:subject:to:references:from:in-reply-to; s=fm1; bh=zRD1Dutsqm4p7r7Ho9/wyKwCs3Rl/LycnpE3lg+XlIk=; b=T2zQj TZCGK+RbPw/Mgz4PdAPm9jFo0adoXN8xfwK8ezp1TDGyW11rmsryA3mkGN/ReegM 3YRpJ4f7XuLfiJyUGommE+ZEw3Z9MQIQJ+tBc2W2J22Z4TzZriqQePrAyD8R1RM9 rTNoCb0AswmWn/AzxYUZQgXz6S4YfyzdK41zs9bjASa9IZnOzQpK/4YYCLDH5kVi KCZ7vJyJIx1iFFyttccnpHjC8BaeZZVVgt6EYepSVTThsDGFOEPsI/PHh9EQL+Ee t/7jq34+TYN1yjKEo72YvfVi18GOrYCGk5mciohq5TbVP+qFGr+o8AH6p7kYJgPf Ktd4ty5kU41KMywkw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:reply-to:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=zRD1Dutsqm4p7r7Ho9/wyKwCs3Rl/LycnpE3lg+XlIk=; b=Jt+vQdzt 0ud8/tjmD6btbShjm4GRELidOgQjij6YLzOeiG2VKkqATBRDH+yzrgP5FYsJrSzx gtFZcNOLdCF5q4KT5LlwE0eqVWvj0Be50lMUpglX7+4LBcEx/30Y1TCbS2CSkMa9 WYmVyQZXXfV2cBzfMbR9mBmpW40By7/xXJgj5b5ibip/pPoNoavGR50AwvPL8nal ULwq7FvxKvGpImaSHXAW54tPwOUYAiXOhY0ABERhti3MejQ5Ilkm29hziCKpgJE/ 98LPNyV4MCOpCxZkt0GxkQ5ORKJ+I/ZMKKaOu89RbJVaf8RfbdNctM9NbnKoGTKh vrWpNb06065ZHw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvdefgedgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtkfffgggfrhfuvfhfhfgjsegrtd erredtfeejnecuhfhrohhmpeflohhsthgvihhnpgfmjhppnhhighhsvghnuceojhhoshht vghinhesshgvtghurhgvrdhkjhhonhhighhsvghnrdhnvghtqeenucggtffrrghtthgvrh hnpeetfeeuleegveetudehleetveelhedvgfetjeegheduheefveekueefgfffteeijeen ucffohhmrghinhepkhhjnhhighhsvghnrdhnohenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehjohhsthgvihhnsehsvggtuhhrvgdrkhhjohhn ihhgshgvnhdrnhgvth X-ME-Proxy: Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 25 Oct 2021 01:47:02 -0400 (EDT) Content-Language: nb-NO In-Reply-To: <87bl4367av.fsf@yahoo.com> Received-SPF: pass client-ip=64.147.123.24; envelope-from=jostein@secure.kjonigsen.net; helo=wout1-smtp.messagingengine.com X-Spam_score_int: -59 X-Spam_score: -6.0 X-Spam_bar: ------ X-Spam_report: (-6.0 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-3.33, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:277707 Archived-At: This is a multi-part message in MIME format. --------------cXxlECEeMsE8dMHtVTMErxTQ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 05.10.2021 13:27, Po Lu wrote: > Philip Kaludercic writes: > >> Po Lu writes: >> >>> Ag Ibragimov writes: >>> >>>> Another reason: VSCode. The damn thing is spreading like a >>>> disease. And now it's even possible to browse code on GitHub, in a >>>> browser, by simply pressing <.> (the dot). I would love to be able to >>>> comfortably browse through elisp code without having to clone it >>>> locally, but none of the existing VSCode Lisp plugins are any good. >>>> For example, there's no equivalent of imenu for Lisp files. You can't >>>> jump to a given function. >>> Isn't the code behind that particular feature proprietary? >> In what sense? GitHub is inherently proprietary, so yes, but what >> about this specific feature is different. > I think it is dangerous for Emacs to "integrate" with such proprietary > software. It would make people gravitate towards that software. > Just to be clear, and so that we're all on the same page: * Whatever software Github runs is proprietary. * The LSP protocol-specification it is based on is fully open, and implemented by lots of (FLOSS) programming-languages. What Ag Ibragimov is asking for here is not integrating with a proprietary product, but implementing the open protocol, to provider better support for Emacs Lisp as a language. If that is perceived as a danger, then I honestly think one might consider re-adjusting once own perception :) -- Vennlig hilsen *Jostein Kjønigsen* jostein@kjonigsen.net 🍵 jostein@gmail.com 🍵 jostein@hufleslufs.no https://jostein.kjønigsen.no --------------cXxlECEeMsE8dMHtVTMErxTQ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit


On 05.10.2021 13:27, Po Lu wrote:
Philip Kaludercic <philipk@posteo.net> writes:


Po Lu <luangruo@yahoo.com> writes:


Ag Ibragimov <agzam.ibragimov@gmail.com> writes:


Another reason: VSCode. The damn thing is spreading like a
disease. And now it's even possible to browse code on GitHub, in a
browser, by simply pressing <.> (the dot).  I would love to be able to
comfortably browse through elisp code without having to clone it
locally, but none of the existing VSCode Lisp plugins are any good.
For example, there's no equivalent of imenu for Lisp files. You can't
jump to a given function.

Isn't the code behind that particular feature proprietary?

In what sense? GitHub is inherently proprietary, so yes, but what
about this specific feature is different.

I think it is dangerous for Emacs to "integrate" with such proprietary
software.  It would make people gravitate towards that software.
Just to be clear, and so that we're all on the same page:

* Whatever software Github runs is proprietary.
* The LSP protocol-specification it is based on is fully open, and implemented by lots of (FLOSS) programming-languages.

What Ag Ibragimov is asking for here is not integrating with a proprietary product, but implementing the open protocol, to provider better support for Emacs Lisp as a language.

If that is perceived as a danger, then I honestly think one might consider re-adjusting once own perception :)

--
Vennlig hilsen
Jostein Kjønigsen

jostein@kjonigsen.net 🍵 jostein@gmail.com 🍵 jostein@hufleslufs.no
https://jostein.kjønigsen.no
--------------cXxlECEeMsE8dMHtVTMErxTQ--