-
-
Notifications
You must be signed in to change notification settings - Fork 391
Incorrect rendering of path to function definition on hover in SublimeText #222
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
Comments
* First attempt at TH support * Update TcModuleResult when generating core * Be a bit more cautious when asking for bytecode * Check need for bytecode not only in source file itself, also in global information * Add a test (based on #212) * Fix test (thanks, @jinwoo) * Split GenerateCore and GenerateByteCode
Is it already solved? Maybe #222 solved it? |
I'm on vacation without access to my devenv; I will be able to look into current rendering of paths not earlier than mid-January. |
@ShrykeWindgrace did you get to check if the issue is reproduced? thanks! |
@jneira thanks for pinging me about this issue, I completely forgot about it (I migrated to VSCode since then). I will try to take a look (this week, most probably; but certainly not today). |
TLDR: the issue is still there. Config: win10, Sublime Text 4 (4126, latest at the time of writing), HLS-1.6.1.0 for ghc-8.10.7. LSP plugin from https://lsp.sublimetext.io/. If there is an option that would allow me provide more info, I'm willing to try. I am not entirely sure whether this is an HLS issue or the LSP plugin issue... VSCode renders these paths with backslashes; what does HLS send? forward slashes or backslashes? |
Tentatively closing as no reports recently. |
Uh oh!
There was an error while loading. Please reload this page.
When I hover on a function, the path to its definition is given without path separator characters (screenshot for illustration):

Config: Win10-1809, hls.exe from the 0.2.1 release (for GHC-8.10.1). SublimeText4 (4079) with the recommended LSP plugin.
The text was updated successfully, but these errors were encountered: