From: Yuan Fu <casouri@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: aqua0210@foxmail.com, 60570@debbugs.gnu.org,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#60570: 29.0.60; Eglot+pyright freeze Emacs when edit a single file in Home director
Date: Thu, 5 Jan 2023 23:17:41 -0700 [thread overview]
Message-ID: <4B02B488-70C2-46A5-8817-C6F103EDD6E4@gmail.com> (raw)
In-Reply-To: <m2bknd2wb7.fsf@foxmail.com>
João Távora <joaotavora@gmail.com> writes:
> 5. Stop opening Python scripts in your $HOME *and* auto-activating Eglot
> in them. You may be auto-activating Eglot with eglot-ensure, but this
> is not recommended precisely because it carries with risks like this.
[...]
>
> I recommend restricting your use of eglot-ensure. It's very overrated
> functionality. M-x eglot will probably only need to be typed once
> or twice in a typical Emacs session.
I use a custom function eglot-soft-ensure which only enables eglot if
there is already a LSP server running for the current project. This way
eglot doesn’t auto-start in which files that I don’t want it to start.
(defun eglot-soft-ensure ()
"Turn on eglot when there is an exising server for the current project."
(require 'eglot)
(when-let* ((project (project-current))
(eglot-server (gethash project eglot--servers-by-project)))
(eglot-ensure)))
Yuan
next prev parent reply other threads:[~2023-01-06 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2bknd2wb7.fsf@foxmail.com>
2023-01-05 21:38 ` bug#60570: 29.0.60; Eglot+pyright freeze Emacs when edit a single file in Home director João Távora
2023-01-06 13:36 ` Eason Huang
2023-01-06 6:17 ` Yuan Fu [this message]
2023-01-06 10:29 ` João Távora
2023-01-07 22:38 ` Yuan Fu
2023-01-05 8:57 Eason Huang
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=4B02B488-70C2-46A5-8817-C6F103EDD6E4@gmail.com \
--to=casouri@gmail.com \
--cc=60570@debbugs.gnu.org \
--cc=aqua0210@foxmail.com \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.com \
/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.