unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master d9b5f618baa 2/4: Eglot: introduce eglot-events-buffer-config
Date: Wed, 27 Dec 2023 17:07:22 +0000	[thread overview]
Message-ID: <CALDnm50P1ftm3JF85kuU8FnrozLRMv4SQNmMQbJt+j3iBNjd2A@mail.gmail.com> (raw)
In-Reply-To: <83le9f8ufh.fsf@gnu.org>

On Wed, Dec 27, 2023 at 4:47 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > +(defcustom eglot-events-buffer-config
> > +  (list :size (or (bound-and-true-p eglot-events-buffer-size) 2000000)
> > +        :format 'full)
> > +  "Configure the Eglot events buffer.
> > +
> > +Value is a plist accepting the keys `:size', which controls the
> > +size in characters of the buffer (0 disables, nil means
> > +infinite), and `:format', which controls the shape of each log
> > +entry (`full' includes the original JSON, `lisp' uses
> > +pretty-printed Lisp).
> > +
> > +For changes on this variable to take effect, you need to restart
> > +the LSP connection.  That can be done by `eglot-reconnect'."
>
> Since changing this defcustom needs some code to be run in order to
> make the changes effective, I wonder whether this defcustom could use
> :set to run that code automatically?

Read above in the same diff:

 @c FIXME: Shouldn't the defcustom do this by itself using the :set
-@c attribute?
+@c attribute?  Maybe not because reconnecting is a complex task.
 @xref{Troubleshooting Eglot}, for when this could be useful.

IOW Reconnecting to a server may trash useful caches, fail due
to numerous reasons, etc...  We don't want to initiate it just
because a user changed a preference.  We could ask for confirmation
though, patches welcome.

João



  reply	other threads:[~2023-12-27 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 16:46 master d9b5f618baa 2/4: Eglot: introduce eglot-events-buffer-config Eli Zaretskii
2023-12-27 17:07 ` João Távora [this message]
2023-12-27 17:29   ` Eli Zaretskii
2023-12-27 17:38     ` João Távora
2023-12-27 18:51       ` Eli Zaretskii
2023-12-27 19:05         ` 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=CALDnm50P1ftm3JF85kuU8FnrozLRMv4SQNmMQbJt+j3iBNjd2A@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).