Always default eglot-strict-mode to nil

it's mostly useful for developers/debugger.  It's better to have the
latter remember to set it than users being hindered by it.

See https://github.com/joaotavora/eglot/issues/131#issuecomment-1191997167

* eglot.el (eglot-strict-mode): default to nil.

diff --git a/lisp/progmodes/eglot.el b/lisp/progmodes/eglot.el
index f9a7d2d1e765d35f7624fe519ec1b1bee4ab2983..2e332c470f9454ca616df06c6316162dc2f17528 100644 (file)
--- a/lisp/progmodes/eglot.el
+++ b/lisp/progmodes/eglot.el
@@ -433,14 +433,12 @@ Here's what an element of this alist might look like:
     (Command ((:title . string) (:command . string)) (:arguments))"))
 
 (eval-and-compile
-  (defvar eglot-strict-mode (if load-file-name '()
-                              '(disallow-non-standard-keys
-                                ;; Uncomment these two for fun at
-                                ;; compile-time or with flymake-mode.
-                                ;;
-                                ;; enforce-required-keys
-                                ;; enforce-optional-keys
-                                ))
+  (defvar eglot-strict-mode
+    '(;; Uncomment next lines for fun and debugging
+      ;; disallow-non-standard-keys
+      ;; enforce-required-keys
+      ;; enforce-optional-keys
+      )
     "How strictly to check LSP interfaces at compile- and run-time.
 
 Value is a list of symbols (if the list is empty, no checks are