I raised an issue on GitHub a little while ago about not being able to use MerlinLocate from inside installed libraries (I can jump to them from my project but then I hit a dead end from there). @trefis advised moving the discussion here.
From what I understand, to jump to definition Merlin needs .merlin files, which Dune auto-generates for your project but are not available for libraries installed through Opam. Excluding them seems to be a deliberate choice, which confuses me, since jumping through definitions and implementations of libraries is important to understand and work with them. My questions are:
- Am I correct that this is a design choice as opposed to a technical challenge, and if so, can this choice be revisited?
- If
.merlinfiles will not be released, what is the best way to get jump to definition working locally? Should I create.merlinfiles in the opam directory tree (and if so what should they look like and where should they be placed)? Or should I symlink to the installed libraries from my project – or copy them to my project – so that Dune is able to generate Merlin files for them? - Is this something that the Duniverse project will resolve?
16 posts - 7 participants