Closed jcs090218 closed 2 years ago
It seems like Cask is ignoring this issue. Do you think the issue should be ignored here? 😕
Loading seq...
../../../../test/eglot-tests.el:Warning: Unknown LSP interface FooObject
../../../../test/eglot-tests.el:Warning: Unknown LSP interface FooObject
../../../../test/eglot-tests.el:Warning: Unknown LSP interface FooObject
../../../../test/eglot-tests.el:Warning: Unknown LSP interface FooObject
../../../../test/eglot-tests.el:Warning: Unknown LSP interface FooObject
../../../../test/eglot-tests.el:Warning: Unknown LSP interface FooObject
dotnet exited with status 1
Hi, I have recently created a tool named Eask. This is designed to replace Cask with as minimal effort as possible. The DSL syntaxes are very similar, and most commands are the same, which should be easy to adapt from Cask to Eask.
Eask also uses the same concept with Eldev. It's written only in Elisp, and the project metadata file (
Eldev
orEask
) is just an elisp file being loaded before the command executions.The major difference is the
Eask
uses yargs and NodeJS runtime to parse command-line arguments. UnlikeCask
orEldev
, usebatch
andbash/sh
.In
.github/workflow/test.yml
jcs090218/setup-emacs
instead ofpurcell/setup-emacs
16
)setup-cask
(replace withsetup-eask
)28.1
ubuntu + macos
withwindows
In
Makefile
emacs --batch ...
with justeask <command>
make checkdoc
andmake lint
but left unused (save it for later)make build
to test packaging and installing.Others
Cask
(replace withEask
)This is totally optional, the major goal is to cutdown/lower the entire CI complexity.