Temper my `eglot' favoritism
This commit is contained in:
parent
d8e2b47af5
commit
59b973a0a0
@ -5990,11 +5990,9 @@ byte code:
|
||||
The [[https://www.emacswiki.org/emacs/PythonProgrammingInEmacs][Python Programming in Emacs]] wiki page lists options to enhance Emacs's
|
||||
built-in ~python-mode~. Here, the focus is on two Emacs packages and four Python
|
||||
packages:
|
||||
1. [[#sec:eglot][Eglot - Emacs polyGLOT: a builtin LSP client since Emacs-29.1]]. The
|
||||
maintainer also contributes to Emacs itself and has a deep understanding of
|
||||
[[https://sheer.tj/the_way_of_emacs.html][the Way of Emacs]]. He refuses to add new features without seeing how they fit
|
||||
into [[https://sheer.tj/the_way_of_emacs.html][the Way of Emacs]] as this discussion on [[https://github.com/joaotavora/eglot/issues/523][org-mode source code blocks]]
|
||||
shows.
|
||||
1. [[#sec:eglot][Eglot - Emacs polyGLOT: a builtin LSP client since Emacs-29.1]] and its author
|
||||
(who is a prolific Common Lisp and Emacs Lisp programmer) has also
|
||||
contributed to other parts of Emacs.
|
||||
2. [[https://jedi.readthedocs.io/en/latest/][Jedi]] is a static analysis tool for Python that is typically used in plugins
|
||||
for editors or integrated development environments. Jedi has a focus on
|
||||
autocompletion and object definition lookup functionality.
|
||||
|
Loading…
Reference in New Issue
Block a user