CLI for building, running, testing, and managing your Emacs Lisp dependencies
Eask was built to use as a package development tool in your Elisp packages. But now, Eask supports various types of Emacs Lisp tasks. It can be used in three major ways:
- Dev tool for Elisp packages
- Dependency management for your configuration
- Run elisp programs for all other purposes
So what are the major differences between Eask and other build tools like Cask, makem.sh, and Eldev, other than the things above?
Good question! Eask is more than a build tool now, it can be used for various purposes! But here are Eask aims to be:
- Consistent enough to sandbox across all systems
- General enough to have Emacsers frequently used commands (
byte-compile
,checkdoc
, etc) - Robust enough to provide useful results even in the presence of user errors
- Dependency-free so that the tool can be run on any platform
P.S. See Why Eask? for more detailed information.
π‘
node
is not required to use Eask!
We have incorporated a range of tests to ensure Eask remains stable throughout its release cycle.
Description | Done | Status |
---|---|---|
Keep the documentation page up to date | β |
Description | Done | Status |
---|---|---|
Compile source and check redefined | β | |
Compatibility check for each Emacs version | β | |
Build executables | β |
Description | Done | Status |
---|---|---|
Test option switches | β |
Description | Done | Status |
---|---|---|
Test ert command |
β | |
Test ert-runner command |
β | |
Test buttercup command |
β | |
Test ecukes command |
β |
Description | Done | Status |
---|---|---|
Webinstall | β |
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.
See COPYING
for details.