New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it work on windows #2
Comments
I'm using the version of eglot found on melpa freshly installed I started emacs 26.1 with emacs& from a Cygwin shell I ran I then disabled flymake-mode and ran I'm using this to add php-server which is where I have php-language-server installed.
I'm going to test using the "host:port" solution next, afterwards I'm going to copy eglot.el and try everything I tried but using eglot.el from github. EGLOT server (~/php-mode) inferior output EGLOT server (~/php-mode) events output
|
The version available on GNU ELPA (not "melpa" yet) is not the latest version, you must either wait until ELPA builds a new package tomorrow, or download "eglot.el" from git using whatever method you want (clone, direct copy from the web interface, etc). Never mind about the With eglot.el from github, if you're lucky, you should be good to go with both the TCP solution and the direct stdin solution. |
Okay, I'll use eglot.el from github for now. I believe starting the server with And connect with localhost:9009 seems to establish a connection.
I'm going to try the newest version from github now. |
Assuming you for this working in the meantime. If I'm wrong, please tell me and I'll reopen. |
# This is the 1st commit message: Add tests of eglot--guess-contact # The commit message joaotavora#2 will be skipped: # Improve name of test utility and add docstring # The commit message joaotavora#3 will be skipped: # Redesign macro used in eglot--guess-contact test
In issue #1, the secondary "hang" problem is probably windows-specific. In version 0.3, commit 12691c2, I pushed some code to make it work on windows and did some testing, but I'm opening this issue to register any more problems.
The text was updated successfully, but these errors were encountered: