Muir Manders
Muir Manders
This fixed it for me as well. Can this be merged?
I get stuck like this sometimes as well. Maybe lsp-shutdown needs to clear out all metadata even if the server process isn't currently running?
FYI if you clear out `lsp--session` (e.g. `M-: (setq lsp--session nil)`) it will retry properly next time you active lsp-mode.
I also have startup issues over tramp that go away with a sleep. I'm going to assume it is the same issue (but note that hack language server crashes instead...
I think we can fix it by echoing a string after the `stty` and waiting for it (so we can be sure the stty has finished before we start writing...
I'm using tramp 2.5.1-pre. #2531 looks like it should work instead of my patch - I'll try it later. But will people be able to use tramp 2.5 on stable...
Apart from some minor bugs, #2531 seems to work great and gives a much better experience overall.
What about cases like `fmt.Print()`? I don't necessarily think it is important, but it is a difference between VSCode so I want to consider it.
This seems to break the normal trigger character behavior. For example, `fmt.` doesn't trigger completions automatically anymore.
It seems like gopls is sending back a "progressive" `filterText`. The client sends a `complete` request after `fmt.P` has been typed, so gopls gives results with a `filterText` that doesn't...