From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pedro Andres Aranda Gutierrez Newsgroups: gmane.emacs.devel Subject: Re: Just an uninformed question Date: Sun, 22 Oct 2023 08:09:54 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d52a44060847f53b" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4513"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 22 08:13:57 2023 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 1quRin-000127-1v for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Oct 2023 08:13:57 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1quRfZ-0001EM-Pu; Sun, 22 Oct 2023 02:10:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1quRfM-0001AD-Hf for emacs-devel@gnu.org; Sun, 22 Oct 2023 02:10:26 -0400 Original-Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1quRfK-0003gY-CB for emacs-devel@gnu.org; Sun, 22 Oct 2023 02:10:24 -0400 Original-Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-53db360294fso3307041a12.3 for ; Sat, 21 Oct 2023 23:10:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697955020; x=1698559820; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Y3rOJ3x1CJJFHtLRs3YGAOihGNionhG7yBtLPM/iMoM=; b=BWKH8KQrRKspG3Im9itreF5iPqvMQGVLOwkkJdplg4ArS7HdJLlse43PDyu8Y2lFPB opM1Rxdv7h+5vwO2ZaaSHQ9bIPQIZljmGN7PuURxmWAOqr4VllXNqAcU2hUmnR7WgOJq RXzvc/kyVqYNM6upjbWz9Y4LYkyMHO7GtLtbpOsYPk2VHa+Ejg1Vtia1UZG4uOYWmNAb EQEMy9+FejwJVFbg2W9Jyh/gvvAa19P0vGBxMvyRPqc3aWESqsyZurEzoH5FqPfLuD4u ikUzHri1Yuu8F9BtNc+bF3lH5ftXCnLgVTJ2dXWFmPzv7PbSCSbOc2eqsNgHUcNYFFSk Hxgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697955020; x=1698559820; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Y3rOJ3x1CJJFHtLRs3YGAOihGNionhG7yBtLPM/iMoM=; b=sVYS0JW1s+NH98Rgr9mDK2h9Q8OCKl9ge9qITFQuSqXxHHf8H/513cbUJAppakxHMa Gu/gg63I1TZ96bUmYPTNBHNWCfvkcHk3jAPBOChv9hw03CQg7eC51vi1EM7JWAW73ty/ ZvHIcCtlutDntpxk8uuMTLY7Kt7maAvh0mtuRjkUTefbOBFZ2zQ1SS3Q+OfF3q4uviSk hNTFSiHk2fNowDKjbTo66OPdfjTbE77Hmcs4KiBvAd8KLfI8XYHISRkBE1uNcUk3rPMT YiDQHZ+BZtaWH+p0fqQherzMoOgtUtv6Rp5caG1xV73oMbTafKYWTebyx+Y54uPMK3YR RMLw== X-Gm-Message-State: AOJu0YyFHQ1mfOBT1W/ntqt5JLmMi6thTW3Vy+rgzwyxjUwKq+9P/kLU 1Sh4Ihm8etJNANQC7sK1+VMZDGCKSgXtYYT46527GxN0/Hk= X-Google-Smtp-Source: AGHT+IH5Bfgb6fi7N87PCzlcaO5rbqBm8Lrj00YNtvkVsoZRq8Fx+Cze3cWwLTWt3lJm7xC9TR+Slb4qUGQTm3Zu8GQ= X-Received: by 2002:a05:6402:5c4:b0:53e:30dc:ef59 with SMTP id n4-20020a05640205c400b0053e30dcef59mr4667692edx.10.1697955020350; Sat, 21 Oct 2023 23:10:20 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=2a00:1450:4864:20::52f; envelope-from=paaguti@gmail.com; helo=mail-ed1-x52f.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311669 Archived-At: --000000000000d52a44060847f53b Content-Type: text/plain; charset="UTF-8" Hi Stefan, +/- correct. I want to explore how difficult it would be to _add_ the possibility of customising eglot with a JSON file in the user-emacs directory. A newbie learning Emacs Lisp might not find it easy to configure eglot with it and, thus, may be "tempted away" from it. The idea should be to make it easier for people to access cool features, not to shy them away because they need a level of ELisp knowledge they don't have (yet). Just my .2 cents from trying to attract people to Emacs, /PA On Sat, 21 Oct 2023 at 13:59, Stefan Kangas wrote: > Pedro Andres Aranda Gutierrez writes: > > > I've been using eglot for some time now and that has implied playing > around > > with different LSPs and their configurations. Before going for the > "complex > > things", like project specific settings, I'm working on a one-fits-all my > > needs config and, yes, I've been writing this in elisp, which was somehow > > convoluted (and maybe not optimal for newbies). > > > > How difficult/acceptable would it be to have a e.g. > > `(locate-user-emacs-file "eglot.json")` file holding the basic > one-fits-all > > configuration in JSON? This files will always be overwritten with a > > .dir-locals.el file for specific projects, of course. > > Sorry, I don't understand what are you proposing. Do you want to > customize Emacs/eglot in JSON instead of in Emacs Lisp? > > Could you please clarify? > -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet --000000000000d52a44060847f53b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Stefan,

+/- correct. I want to explore how= difficult it would be to _add_ the possibility
of customisin= g eglot with a JSON file in the user-emacs directory. A newbie
le= arning Emacs Lisp might not find it easy to configure eglot with it and, th= us,
may be "tempted away" from it. The idea should be t= o make it easier for people
to access cool features, not to shy t= hem away because they need a level of
ELisp knowledge they don= 9;t have (yet).

Just my .2 cents from trying to at= tract people to Emacs,
/PA=C2=A0

On Sat, 21 Oct 2023 = at 13:59, Stefan Kangas <stefa= nkangas@gmail.com> wrote:
Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> I've been using eglot for some time now and that has implied playi= ng around
> with different LSPs and their configurations. Before going for the &qu= ot;complex
> things", like project specific settings, I'm working on a one= -fits-all my
> needs config and, yes, I've been writing this in elisp, which was = somehow
> convoluted (and maybe not optimal for newbies).
>
> How difficult/acceptable would it be to have a e.g.
> `(locate-user-emacs-file "eglot.json")` file holding the bas= ic one-fits-all
> configuration in JSON? This files will always be overwritten with a > .dir-locals.el file for specific projects, of course.

Sorry, I don't understand what are you proposing.=C2=A0 Do you want to<= br> customize Emacs/eglot in JSON instead of in Emacs Lisp?

Could you please clarify?


--
Fragen sind nicht da, um bea= ntwortet zu werden,
Fragen sind da um gestellt zu werden
= Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should ru= n a leader-deposed hook here, but we can't yet

--000000000000d52a44060847f53b--