-
Notifications
You must be signed in to change notification settings - Fork 60
/tmp/lsp.log
doesn't work for a shared server
#47
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
Closed
hoichi opened this issue
Dec 11, 2020
· 1 comment
· Fixed by rescript-lang/rescript-editor-support#42
Closed
/tmp/lsp.log
doesn't work for a shared server
#47
hoichi opened this issue
Dec 11, 2020
· 1 comment
· Fixed by rescript-lang/rescript-editor-support#42
Comments
As a workaround, setting a |
cristianoc
added a commit
to rescript-lang/rescript-editor-support
that referenced
this issue
Dec 14, 2020
cristianoc
added a commit
to rescript-lang/rescript-editor-support
that referenced
this issue
Dec 14, 2020
cristianoc
added a commit
to rescript-lang/rescript-editor-support
that referenced
this issue
Dec 14, 2020
cristianoc
added a commit
that referenced
this issue
Jan 6, 2021
- Fix type shown when hovering on record fields (see #52), and doc comments for records. - Fix issue where type variables are printed with global renaming when hovering or autocompleting a module (see rescript-lang/rescript-editor-support#38). - Fix issue where a log file was always created (see #47). - Add support for hover on the id of toplevel module definitions (```module Id = ...```).
chenglou
pushed a commit
to chenglou/rescript-editor-support
that referenced
this issue
Apr 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the language server crashes for me when I work on a remote server (via a Remote - SSH plugin), with the following message:
And this is because
/tmp/lsp.log
is created and owned by my teammate, not by me. Deleting the file resolves the problem.But even if we figure out the file permissions, won't it mean that only one person at a time is able to work at one particular machine? That would be unfortunate because the server is meant to be used for development by many people at once.
The text was updated successfully, but these errors were encountered: