ocp-index does that, in the most simple way possible: the file is parsed to find any scope-changing constructs (open, include, functor parameters...), then it tries to resolve the identifier, reading any .cmi file corresponding to an open module it can find to check for a match.

It's not 100% perfect (e.g. in its current version, it won't distinguish identifiers corresponding to values, field names, or types), but it works extremely well in practice and, using it, pulling hair because I have to lose time looking up an identifier in the presence of 'open' statements is a thing of the past. Just run '(ocp-index-print-info-at-point)' in emacs (and from the shell, it's 'ocp-index print IDENT --context FILE:LINE:COL "%p"')

Of course, it's not as light-weight, but if you have Merlin configured on your project and working, that's even better: in either case you get jump-to-source which also gives that information, and Merlin is more accurate.



> - Gerd Stolpmann, 15/07/2016 19:04 -
> Am Freitag, den 15.07.2016, 12:13 -0400 schrieb Hendrik Boom:
> > Or is there some kind of code browsing tool that explicates all this?
> 
> I don't know any tool that just shows the full path of identifiers.
> Merlin could do it (has all infos) but it doesn't so far. It "only"
> shows the type (also useful, but in a different way).
> 
> Gerd
>