Releases: emacs-eldev/eldev
Eldev 1.10.3
Fixed: compiling test files now also uses test-specific dependencies if those are specified using (eldev-add-extra-dependencies 'test ...)
. Previously, such dependencies would only be used for executing test .el
files and an attempt to compile them would result in an error.
Eldev 1.10.2
This release updates compatibility layer for relint
to use version 2.0. Also, Eldev now heuristically adds a hint to some errors coming from Docker/Podman invocations.
Eldev 1.10.1
This release fixes a bug that recently added eldev-display-indirect-build-stdout
causes in setups with local dependencies in packaged
loading mode.
Eldev 1.10
Several new features:
- Support for another testing framework: Doctest. Unlike the three already supported, this one doesn’t have separate test files, but instead embeds testcases inside your normal source code, in docstrings.
- New command
podman
adds direct support for Podman, which is largely the same as that for Docker. - Eldev should now work correctly with rootless Docker and Podman installations.
- Projects can now optionally display indirect build information by setting variable
eldev-display-indirect-build-stdout
in fileEldev
. - Improved diagnostics when a package cannot be installed (e.g. from GNU ELPA) due to invalid or outdated signature.
- Other minor fixes and improvements.
Eldev 1.9.1
This is a bug-fix release:
- Eldev was not correctly handling projects that were used as Emacs built-ins, for example Org.
- Project
.el
file byte-compilation would choke on files withno-byte-compile
local variable. Autoload files and package descriptors, although having such a setting too, were handled correctly, but only as a special case.
Eldev 1.9
This release adds a way to disable dependency management and use Emacs load-path
directly. This is needed to build Elisp packages for GUIX, as there is no network access and thus standard package archives cannot be used. This new mode is not recommended for use otherwise.
Eldev 1.8.2
This release fixes command info
to work properly in projects with source subdirectories; previously it would die with an internal error.
Documentation now mentions new package flymake-eldev that is similar to preexisting flycheck-eldev, but for built-in Emacs Flymake rather than external Flycheck.
Eldev 1.8.1
This release fixes a bug in the newly added source directory functionality that was triggered when a project specified exactly one such directory and used any plugin, e.g. autoloads
.
Eldev 1.8
A new major-feature release:
- Support for source subdirectories needed for some large projects, e.g. CIDER. If configured for a project, Eldev will look for the source code files not in the root, as it does by default, but in the specified subdirectory.
- Minor improvement for test runner
concise
, which was added back in 1.6. - A couple more workarounds for Emacs bug can make your life easier when testing on a CI server or using Docker.
Eldev 1.7
This release contains a lot of assorted bugfixes in various places, as well as a couple minor new features:
- Loading mode
compiled-on-demand
no longer hides compilation warnings, which might be very important at times. - New loading mode
noisy-compiled-on-demand
is just likecompiled-on-demand
, except it prints message “ELC ...” whenever it compiles anything. It goes into stdout and potentially in the middle of normal program output, but it’s your decision whether to use it. - Changed behavior of no-argument option
--force
(-f
) in build system (including byte-compilation). Now it forces building only of targets otherwise mentioned on the command line. New option--force-all
or-F
, not accepting arguments at all, inherits the old semantics. - New functions
eldev-parse-command-line
andeldev-inherit-options
to simplify definition of project-specific commands. See their documentation inside Emacs. - Improved performance of ERT in certain projects that contain
should...
assertions in large loops.