From: "João Távora" <joaotavora@gmail.com>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
Yuan Fu <casouri@gmail.com>,
Emacs developers <emacs-devel@gnu.org>,
Stephen Leake <stephen_leake@stephe-leake.org>
Subject: Re: Explain a bit more on how to configure language server in Eglot's manual
Date: Mon, 6 Mar 2023 18:32:43 +0000 [thread overview]
Message-ID: <CALDnm52snC399nzKDZVRZQA_Gqcjd4M=hO41XxTTxpCot4XxUA@mail.gmail.com> (raw)
In-Reply-To: <87mt4ppwtv.fsf@gmail.com>
On Mon, Mar 6, 2023 at 6:18 PM Augusto Stoffel <arstoffel@gmail.com> wrote:
> > add-dir-local-variable with new edit-in-buffer option, an eval option,
> > and a fill-in-existing-value option. As a bonus, all those are
> > orthogonal, so you can do 100 + 100 + 100.
>
> Fair enough. I think you might be overestimating the general interest
> in those things and underestimating the amount of glue code Eglot would
> still need, but it's just a hunch.
What glue code? M-x add-dir-local-variable (or M-x add-project-local-variable
which is a just a very thing shim on top of the other), then select
eglot-workspace-configuration, then edit the value and you're done.
> Anyway, my offer to make the
> eglot-show-workspace-configuration buffer editable remains open. (If
> you find a better solution you should probably remove e-s-w-c because it
> feels like a hack in the current state.)
Not a hack, really. eglot-show-workspace-configuration shows the actual
configuration in JSON format. That's useful and LSP specific, so it
belongs in Eglot. Fredrik Bergroth added it because that is what is
sent to the server and is really good for debug purposes and
communicating with server devs, for example. So it's not subsumed
by C-h v, for example.
João
next prev parent reply other threads:[~2023-03-06 18:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 4:45 Explain a bit more on how to configure language server in Eglot's manual Yuan Fu
2023-03-05 22:36 ` [SPAM UNSURE] " Stephen Leake
2023-03-06 0:16 ` João Távora
2023-03-06 22:28 ` Yuan Fu
2023-03-07 11:59 ` João Távora
2023-03-08 13:27 ` Augusto Stoffel
2023-03-08 13:54 ` João Távora
2023-03-08 15:01 ` Augusto Stoffel
2023-03-08 19:43 ` João Távora
2023-03-08 20:43 ` Augusto Stoffel
2023-03-09 9:43 ` João Távora
2023-03-08 23:19 ` Yuan Fu
2023-03-09 8:18 ` Augusto Stoffel
2023-03-09 17:20 ` Juri Linkov
2023-03-10 6:26 ` Yuan Fu
2023-03-10 7:59 ` João Távora
2023-03-09 17:40 ` João Távora
2023-03-09 18:05 ` Juri Linkov
2023-03-09 18:32 ` Augusto Stoffel
2023-03-09 8:28 ` Explain a bit more on how to configure language server in Eglot's manual' Augusto Stoffel
2023-03-08 15:24 ` Explain a bit more on how to configure language server in Eglot's manual Yuri Khan
2023-03-08 15:27 ` João Távora
2023-03-08 15:52 ` Yuri Khan
2023-03-08 16:03 ` João Távora
2023-03-09 11:18 ` [SPAM UNSURE] " João Távora
2023-03-10 6:23 ` Yuan Fu
2023-03-14 18:09 ` Michael Eliachevitch
2023-03-14 18:53 ` João Távora
2023-03-14 22:27 ` [PATCH] " Michael Eliachevitch
2023-03-15 11:49 ` Michael Eliachevitch
2023-03-15 12:35 ` Eli Zaretskii
2023-03-15 12:52 ` Michael Eliachevitch
2023-03-15 18:54 ` João Távora
2023-03-15 19:26 ` Michael Eliachevitch
2023-03-16 0:09 ` João Távora
2023-03-06 10:34 ` Augusto Stoffel
2023-03-06 10:51 ` João Távora
2023-03-06 11:00 ` Augusto Stoffel
2023-03-06 11:13 ` João Távora
2023-03-06 11:30 ` Pedro Andres Aranda Gutierrez
2023-03-06 11:46 ` João Távora
2023-03-06 13:08 ` Augusto Stoffel
2023-03-06 13:50 ` João Távora
2023-03-06 16:10 ` Augusto Stoffel
2023-03-06 16:25 ` João Távora
2023-03-06 18:18 ` Augusto Stoffel
2023-03-06 18:32 ` João Távora [this message]
2023-03-06 20:16 ` Pedro Andres Aranda Gutierrez
2023-03-06 21:13 ` Augusto Stoffel
2023-03-06 21:38 ` João Távora
2023-03-06 13:01 ` Augusto Stoffel
-- strict thread matches above, loose matches on Subject: below --
2023-03-12 12:09 Pedro Andres Aranda Gutierrez
2023-03-12 19:52 ` João Távora
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='CALDnm52snC399nzKDZVRZQA_Gqcjd4M=hO41XxTTxpCot4XxUA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=arstoffel@gmail.com \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=paaguti@gmail.com \
--cc=stephen_leake@stephe-leake.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).