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
Configuration:
OCaml 4.14.0 - Emacs 29.0.50 - Tuareg (v3.0.1) - Merlin (v4.6-414, for OCaml 4.14.0) - Linux Box x86_64
After having tried several OCaml files (some very old and in any case without using Dune)
it seems that the mere presence of a 'dune-project' file (even empty!) is enough to activate Flycheck-ocaml.
Is this behavior general?
If so, it would be good to modify the README by specifying this simplification.
(No need to setup a Dune project and run dune build)
The text was updated successfully, but these errors were encountered:
temyurchenko
added a commit
to temyurchenko/flycheck-ocaml
that referenced
this issue
Jan 6, 2024
Problem: some projects don't use Dune, while using Merlin, configured
with the .merlin file. `flycheck-ocaml` is only turned on if the
«dune-project» file is present though. As a result,
`flycheck-ocaml` is disabled for such projects.
Solution: enable the `flycheck-ocaml` checker if either dune-project
or .merlin are present.
In a round-about way this fixesflycheck#15. People who don't use Dune, don't
need to create an empty dune-project to use the checker, which was
misleading.
Problem: some projects don't use Dune, while using Merlin, configured
with the .merlin file. `flycheck-ocaml` is only turned on if the
«dune-project» file is present though. As a result,
`flycheck-ocaml` is disabled for such projects.
Solution: enable the `flycheck-ocaml` checker if either dune-project
or .merlin are present.
In a round-about way this fixesflycheck#15. People who don't use Dune, don't
need to create an empty dune-project to use the checker, which was
misleading.
Configuration:
OCaml 4.14.0 - Emacs 29.0.50 - Tuareg (v3.0.1) - Merlin (v4.6-414, for OCaml 4.14.0) - Linux Box x86_64
After having tried several OCaml files (some very old and in any case without using Dune)
it seems that the mere presence of a 'dune-project' file (even empty!) is enough to activate Flycheck-ocaml.
Is this behavior general?
If so, it would be good to modify the README by specifying this simplification.
(No need to setup a Dune project and run dune build)
The text was updated successfully, but these errors were encountered: