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

[Dmitry Gutov]

On 22/11/22 23:40, João Távora wrote:
> Rather it's the fact that the monorepo is clearly organized into loosely 
> coupled
> sub-projects and very often (but not always) it makes sense to do 
> sub-project
> wide file-finding and reference-finding.  No LSP/Eglotness involved at all.

Speaking of monorepos, it seems to me that the boundaries between 
subprojects (or just nested projects) might not be defined by 
language-based separation of app directories, but rather by 
organizational needs (e.g. how teams are split). Teams could be 
backend-frontend-some-other-end, or they could be full-stack too.

IOW, the "subproject" structure needed by Eglot and one that looks 
natural to developers might quite well be different.

> As I explained earlier, it would also help if project-files weren't so 
> "flat list"
> oriented and allowed generalized collections, such as my completion table
> based on a very fast external indexer.

That's a separate feature request.