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/msg01397.html below:

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Alfred M. Szmidt Subject: Re: Eglot, project.el, and python virtual environments Date: Mon, 21 Nov 2022 10:41:07 -0500

   > I spent some time looking at eglot.el and project.el, and was mostly
   > surprised to find how little they need to know about each other.

   In particular, project.el knows nothing of eglot.el :-), as it should.

If eglot can make project.el better (or vice versa), then why not?
This seems like a short sighted absolutism.

Re: Eglot, project.el, and python virtual environments, (continued)
- Re: Eglot, project.el, and python virtual environments, Philip Kaludercic, 2022/11/16
  - Re: Eglot, project.el, and python virtual environments, Eric Abrahamsen, 2022/11/17
- Re: Eglot, project.el, and python virtual environments, North Year, 2022/11/17
  - Re: Eglot, project.el, and python virtual environments, Eric Abrahamsen, 2022/11/17
- Re: Eglot, project.el, and python virtual environments, Stephen Leake, 2022/11/19

Prev by Date: Delegating user-reserved key binding space definition to users
Next by Date: Re: scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling elisp constants into static data.
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