Skip to content
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

How can I get merlin to treat files with unusual names "normally"? #1262

Closed
fdopen opened this issue Feb 5, 2021 · 2 comments · Fixed by ocaml/dune#4264
Closed

How can I get merlin to treat files with unusual names "normally"? #1262

fdopen opened this issue Feb 5, 2021 · 2 comments · Fixed by ocaml/dune#4264

Comments

@fdopen
Copy link
Contributor

fdopen commented Feb 5, 2021

dune 2.8 no longer generate .merlin files. Files with unusual names are now not longer treated in the usual way, e.g:

ocamlmerlin single dump-configuration -filename msource.foo.ml < /dev/null | jq:

    "merlin": {
      "build_path": [],
      "source_path": [],
      "cmi_path": [],
      "cmt_path": [],
      "flags_applied": [], ...

With .merlin files however, msource.foo.ml was processed like msource.ml (build_path, source_path, etc. are filled as expected and type hints, etc. are provided in the usual way.)

How do I get the old behavior back under the new setup?

@voodoos
Copy link
Collaborator

voodoos commented Feb 15, 2021

Thanks for your report.

How are these files compiled ? I guess you have rules to copy these to files with "usual" names ?

@fdopen
Copy link
Contributor Author

fdopen commented Feb 15, 2021

Yes, there is usually a rule to generate a file with a regular suffix (similiar to *.cppo.ml files), see e.g:
https://github.com/fdopen/ppx_cstubs/blob/962a2d5e98e0a26b58e80019592d84586bf4ce37/examples/dune-project/src/lib/dune#L12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants