From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56407@debbugs.gnu.org
Subject: bug#56407: 29.0.50; desktop.el shouldn't be saving/restoring eglot--managed-mode, which is not for interactive use
Date: Tue, 05 Jul 2022 23:52:35 +0100 [thread overview]
Message-ID: <87let7p3yk.fsf@gmail.com> (raw)
In-Reply-To: <83v8sb73ga.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 05 Jul 2022 22:40:53 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Your change also precludes anyone to have such
> a mode restored, ever -- why?
I'm sorry, I realize I didn't answer this part of your email earlier.
eglot--managed-mode is a special minor mode: although the function is
created by define-minor-mode, it is not meant to be turned interactively
for example. It needs certain preconditions to be true before turning
it on and off. If this was all there it could perhaps be arranged with
some of those special function, but a very important detail here is that
these preconditions cannot be on per-buffer. The most important of them
regards a connection to an LSP server which has a view over _all_
buffers in a certain major mode within a certain project. Eglot has
machinery to carefully manage this, and I'm not sure it is easy or wise
to transfer or invoke that machinery in desktop.el's mode-restoring
functions.
Also, eglot--managed-mode is really an implementation detail that is
subject to change. Not only theoretically, but practically, too, as I
ponder the ability to have more than one server active for any given
buffer at a time.
João
next prev parent reply other threads:[~2022-07-05 22:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 19:34 bug#56407: 29.0.50; desktop.el shouldn't be saving/restoring eglot--managed-mode, which is not for interactive use João Távora
2022-07-05 19:40 ` Eli Zaretskii
2022-07-05 19:53 ` João Távora
2022-07-06 2:29 ` Eli Zaretskii
2022-07-06 8:12 ` João Távora
2022-07-06 11:09 ` Eli Zaretskii
2022-07-06 11:30 ` João Távora
2022-07-06 11:37 ` Lars Ingebrigtsen
2022-07-06 12:48 ` Eli Zaretskii
2022-07-06 12:59 ` João Távora
2022-07-06 13:12 ` Eli Zaretskii
2022-07-06 13:19 ` João Távora
2022-07-06 13:23 ` João Távora
2022-07-06 13:39 ` Stefan Kangas
2022-07-06 13:47 ` João Távora
2022-07-06 13:52 ` Stefan Kangas
2022-07-06 13:52 ` Lars Ingebrigtsen
2022-07-06 13:59 ` João Távora
2022-07-05 22:52 ` João Távora [this message]
2022-07-06 2:34 ` Eli Zaretskii
2022-07-06 8:27 ` João Távora
2022-07-05 19:41 ` Lars Ingebrigtsen
2022-07-05 19:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87let7p3yk.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=56407@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.