From: João Távora <joaotavora@gmail.com>
Date: Thu, 20 Oct 2022 10:20:30 +0000 (+0100)
Subject: Fix Eglot manual's description of eglot-workspace-configuration
X-Git-Tag: emacs-29.0.90~1616^2~524^2~3^2~1
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=2a9797b422fe8a28bfaab49974ea2be21ae2502e;p=emacs.git

Fix Eglot manual's description of eglot-workspace-configuration

* doc/misc/eglot.texi (Customizing Eglot)
(eglot-workspace-configuration): Explain that plist may be
arbitrarily complex and correctly identify nil as the Elisp
equivalent to JSON null.
---

diff --git a/doc/misc/eglot.texi b/doc/misc/eglot.texi
index caf09769b49..a05e7fd7ee8 100644
--- a/doc/misc/eglot.texi
+++ b/doc/misc/eglot.texi
@@ -964,11 +964,12 @@ this variable should be a property list of the following format:
 @noindent
 Here @code{:@var{server}} identifies a particular language server and
 @var{plist} is the corresponding keyword-value property list of one or
-more parameter settings for that server.  That list of parameters is
-serialized to JSON by Eglot and sent to the server.  For that reason
-JSON values @code{true}, @code{false}, and @code{@{@}} should be
-represented in the property lists as Lisp symbols @code{t},
-@code{:json-false}, and @code{nil}, respectively.
+more parameter settings for that server, serialized by Eglot as a JSON
+object.  @var{plist} may be arbitrarity complex, generally containing
+other keywork-value property sublists corresponding to JSON subobjects.
+The JSON values @code{true}, @code{false}, @code{null} and @code{@{@}}
+are represented by the Lisp values @code{t}, @code{:json-false},
+@code{nil}, and @{eglot-@{@}}, respectively.
 
 @findex eglot-show-workspace-configuration
 When experimenting with workspace settings, you can use the command