Re: User experience: eglot configuration

[Pedro Andres Aranda Gutierrez]

Hi,

I'm basically saying that when you do

M-x eglot-show-workspace-configuration

what it shows is JSON, which is nice to read, BTW. 

So why not defining a way to place a default configuration for eglot written in JSON in ~/.emacs.d or wherever init.el happens to be?

Or even a way of exporting and using the output buffer of eglot-show-workspace-configuration as a kickstarter.

Always as a complement to what is normally done with .dir-locals.el (which would, of course, take precedence over the JSON stuff). 

And, once you are proficient enough in elisp, you can explore the joys and frustrations of natively manipulating eglot-default-workspace-configuration.

Just to lower the entry barrier by a fraction.

Best, /PA

 

On Wed, 29 Jan 2025 at 21:01, chad <yandros@gmail.com> wrote:

On Wed, Jan 29, 2025 at 8:06 AM Pedro Andres Aranda Gutierrez <paaguti@gmail.com> wrote:

... Or rephrasing:

if the LSP wants JSON, why elisp -> JSON and not JSON directly? Would be easier

to debug...

Am I misunderstanding, or are you saying that it would be easier to
write raw JSON than lisp? That strikes me as unlikely, so I worry that
you're thinking "people find it easier to use giant piles of GUI and
_javascript_ code (electron, VSCode) that writes files for them (that
happen to be in JSON) than to themselves write configuration in lisp
syntax", which seems like it might be true but definitely not the same
thing.

 

Apologies if I'm confused. Thanks in advance.

~Chad

--

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