Dominik Schrempf

Anybody here? Is this something we can/should implement? Would a PR be welcome?

Ah, thanks for asking. Often, the UI shows just above the area I am currently editing. In this case, I want the UI to show up on the other side...

The code I am using at the moment is below. The function `lsp-ui-doc--move-frame` is copy-paste, also checking the `'other` case of `lsp-ui-doc-side`. Let me know if you want a PR....

Yes, if this is your workflow. In theory, we could limit the amount of output. The underlying library redirects output to a temporary file and then reads this temporary file....

Could it be that you started HLS in the project (i.e., the file) already before changing the `.cabal` file? There is a known limitation that HLS does not pick up...

We need more information to debug your session. But you can also get active, and have a look at `*lsp-` buffers. I expect your workspace root to be off. When...

For reference, this is the debug log I get when running GHC 910, HLS on master: ``` 2025-04-23T18:08:06.640684Z | Debug | Finished: eval.getUriContents Took: 0.00s 2025-04-23T18:08:06.641450Z | Debug | Finished...

Hi! You marked this as a good first issue. Could you give us some guidance as to how we would proceed in implementing this? The grammars seem to be git...

> In the stdout case I believe the output is sent in the LSP channel directly to the editor as is. If you're lucky, the editor's LSP parser will handle...

I agree, this is annoying. I do think though, that completion after symbols after/between `'` would be super helpful, as well as completion of module names after/between `"`.