·environment macOS Mojave 10.14.6 GNU Emacs 26.3
When I tried to install emacs-jedi on mac, I got hooked. Originally I was using jedi, but I tried to reinstall it because the environment of python itself changed. By the way, I remember it was hard when I first installed it.
By the way, here is the original setting.
(add-hook 'python-mode-hook 'jedi:setup)
(setq jedi:complete-on-dot t)
Is mac and jedi incompatible? For example, there is such information. https://github.com/tkf/emacs-jedi/issues/346
Also, it's confusing to go to python in virtualenv by default ...
I was able to install jedi itself from M-x package-list-package
without any problems, but I got an error with M-x jedi: install-server
.
deferred error : (error "Deferred process exited abnormally:
command: virtualenv
exit status: exit 1
event: exited abnormally with code 1
buffer contents: \"FileExistsError: [Errno 17] File exists: '/usr/local/opt/[email protected]/bin/pytho\
n3.8' -> '/Users/username/.emacs.d/.python-environments/default/bin/python'
\"")
In the documentation http://tkf.github.io/emacs-jedi/latest/#jedi:install-server
The environment is in ~ / .emacs.d / .python-environments / default /
Because there is, I thought that it was because the old python environment remained here, so I deleted this
rm -r .emacs.d/.python-environments/default
Then I ran M-x jedi: install-server
again, but I'm sorry I got the following error.
Traceback (most recent call last):
File "/Users/username/.emacs.d/.python-environments/default/bin/jediepcserver", line 5, in <module\
>
from jediepcserver import main
ModuleNotFoundError: No module named 'jediepcserver'
Process epc:server:3 exited abnormally with code 1
I was saved by this article ...! http://proglab.blog.fc2.com/blog-entry-46.html
To summarize this article
After all, I realized that if jedi, epc, jediepcserver are installed, I don't have to build a virtual environment with virtualenv ...
pip install --upgrade ~/.emacs.d/elpa/jedi-core-What
To the configuration file (ex. ~ / .Emacs)
(setq jedi:server-command (list (executable-find "jediepcserver")))
Should be added.
So, I actually solved it with this even at my own hands!
The jedi is so convenient that I'm really grateful that it's back in use. If anyone knows an effective countermeasure against the above error, please let me know.
Recommended Posts