RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg01205.html below:

Re: Eglot, project.el, and python virtual environments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Eli Zaretskii Subject: Re: Eglot, project.el, and python virtual environments Date: Fri, 18 Nov 2022 17:17:08 +0200

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Phil Sainty <psainty@orcon.net.nz>,  Dmitry Gutov <dgutov@yandex.ru>,
>   theophilusx@gmail.com,  emacs-devel@gnu.org
> Date: Fri, 18 Nov 2022 10:06:49 -0500
> 
> > Let me remind you that Eglot already supports a kind of "sub-project":
> > it uses the same LSP server only for those source files in a project
> > that share the same major mode.
> 
> IIUC this is not always the right thing to do (for some multilanguage
> projects where the LSP server supports similarly multiple languages).

I didn't say it was _always_ TRT to do.  The question is: how
frequently is this TRT?  If it's a common situation, then the
exceptional situations need a specialized solution, but that solution
doesn't need to be in project.el.

Re: Eglot, project.el, and python virtual environments, (continued)

Prev by Date: Re: Eglot, project.el, and python virtual environments
Next by Date: Re: Eglot, project.el, and python virtual environments
Previous by thread: Re: Eglot, project.el, and python virtual environments
Next by thread: Re: Eglot, project.el, and python virtual environments
Index(es):
- Date
- Thread

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4