Open ManasJayanth opened 1 month ago
Thanks for your report, I was able to reproduce it.
So it is due to the fact the the pparse module is copied via a Dune rules and Merlin doesn't use the added line directive to resolve the correct path. Copy directives support is very lacking right now.
I used Emacs with Eglot with
opam exec -- ocamllsp
as the language server command.In
mpipeline.ml
when I try to run go-to-definition onPparse.apply_pp
- it fails. If it run it on justPparse
it takes me to thecompiler-libs
instead of taking me to vendored/patched source files insrc/ocaml/driver/pparse.ml
https://github.com/ocaml/merlin/blob/c76379cdaeb429459c9ecfc2990936eb8a36980a/src/kernel/mpipeline.ml#L240-L242
additional information