flymake-eldev

Make Flymake use proper dependencies in Eldev projects.

For a project to be detected, it must contain file Eldev or Eldev-local in its root directory, even if Eldev doesn’t strictly require that.

💡	If you are using Flycheck and not Flymake, check out a similar project, flycheck-eldev

Features

• No additional steps to be performed from the command line, not even eldev prepare.

• Project dependencies are seen by Flymake in Emacs. Similarly, if a package is not declared as a dependency of your project, Flymake will complain about unimportable features or undeclared functions.

• Everything is done on-the-fly. As you edit your project’s dependency list in its main .el file, added, removed or mistyped dependency names immediately become available to Flymake (there might be some delays due to network, as Eldev needs to fetch them first).

• Additional test dependencies (see eldev-add-extra-dependencies) are seen from the test files, but not from the main files.

• Also checks files Eldev and Eldev-local (as long as they are byte-compilable, but this is a common Flymake requirement). Detect wrong (eldev-…​) function calls as you type!

Installation

Download and install the package from MELPA Stable or MELPA. No further steps necessary: once the package is installed, it is active and Flymake will detect any Eldev projects on-the-fly.

For the extension to have any effect, you need to install Eldev.

If you want to deactivate the package for some reason, set variable flymake-eldev-active to nil.