You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
The link to Slack is wrong on the "readme" page.
I would like to use omnisharp with emacs + tramp + eglot.
When I use the same Omnisharp version with emacs + eglot on my local system everything is working well.
I think the environment is different with tramp (ssh connection to the server).
I would like to see what is the problem but I can't see the stdout / stderr or maybe there is nothing on these channels ...
I was seeing that the OmniSharp is started because I saw the processes but there is no answer for the first jsonrpc message. The first message is ~same on localhost and the "ssh/tramp" connection ...
Except that the message contains the "processId:null" what can be problem ... ?
When I start the OmniSharp (without -lsp) from command line on the server then everthing seems good.
My plan is to write the log from OmniSharp to a file to see what is the problem.
Is there any configuration how I can do this ?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi,
The link to Slack is wrong on the "readme" page.
I would like to use omnisharp with emacs + tramp + eglot.
When I use the same Omnisharp version with emacs + eglot on my local system everything is working well.
I think the environment is different with tramp (ssh connection to the server).
I would like to see what is the problem but I can't see the stdout / stderr or maybe there is nothing on these channels ...
I was seeing that the OmniSharp is started because I saw the processes but there is no answer for the first jsonrpc message. The first message is ~same on localhost and the "ssh/tramp" connection ...
Except that the message contains the "processId:null" what can be problem ... ?
When I start the OmniSharp (without -lsp) from command line on the server then everthing seems good.
My plan is to write the log from OmniSharp to a file to see what is the problem.
Is there any configuration how I can do this ?
Thanks in advance!
The text was updated successfully, but these errors were encountered: