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
I am using WSL and dune. I have made a very simple project:
I have built it with dune build, it compiles and works as you would expect. The hover definition on the A module from the a.ml file works just fine:
but when i use "Go to defintion" (Ctrl+click / F12) it opens the wrong file:
For some reason it opens A.ml instead of a.ml (Note that A.ml is not a real file in my project, so everything in the file will be marked as error), I cannot find any way to fix this behaviour, the go to definition thing doesn't seem to be able to comprehend that the module has capitalized first letter while the actual file is lower case.
The text was updated successfully, but these errors were encountered:
I have the same problem working in a vscode devcontainer. Also in the capitalized file that is opened all the other modules don't get recognized and give a "Unbound Module xyz" message.
Is there already a workaround for this?
I am using WSL and dune. I have made a very simple project:
I have built it with dune build, it compiles and works as you would expect. The hover definition on the A module from the a.ml file works just fine:
but when i use "Go to defintion" (Ctrl+click / F12) it opens the wrong file:
For some reason it opens A.ml instead of a.ml (Note that A.ml is not a real file in my project, so everything in the file will be marked as error), I cannot find any way to fix this behaviour, the go to definition thing doesn't seem to be able to comprehend that the module has capitalized first letter while the actual file is lower case.
The text was updated successfully, but these errors were encountered: