Re: [SPAM UNSURE] Explain a bit more on how to configure language server in Eglot's manual

[João Távora]

Yuan, please show the patch to Eglot's manual and let's work from
there.

I'm also OK with adding more examples, and work on simplifying the
per-project configuration workflow, maybe by somehow making it
easier to translate that dotted path notation into the nested JSON
object that the server is ultimately looking for.

By the way, it's per-project server configuration that you're
presumably after when looking at eglot-workspace-configuration,
NOT per-user.

A per-user thing would be :initializationOptions or custom
command-line arguments in eglot-server-programs, or even a
special ~/.foorc file that the server reads (rust analyzer doesn't
seem to have one, though, but clangd does).  The reason I bring
up the distinction is that, in many cases (but not all of course),
the user is actually interested in that, but strays from
the objective and ends up the same configuration over all her
different projects.

If this distinction is not clear in the manual, either, it should
be made so.

Reading the docs, rust-analyzer allows per-user configuration via
:initializationOptions.  The syntax and supported options are
usually the same but the difficulties and confusion associated
with ~/.dir-locals.el are not there.

João