Description
I installed Eask and created an Eask file by migrating all my dependencies from Cask. The deps installed successfully with this warning:
Warning (initialization): Your ‘load-path’ seems to contain
your ‘.emacs.d’ directory:~/.emacs.d/
This is likely to cause problems...
Consider using a subdirectory instead, e.g.: ~/.emacs.d/lisp
I start emacs by CLI or the dedicated OSX emacs package, which looks for init.el in ~/.emacs.d which loads all my el files configuration (assuming the dependencies are installed). Emacs needs to know where to find these dependencies and in the past this was done by loading cask file and calling cask-initialize. Currently loading Emacs fails since it doesn't know where Eask dependencies are installed.
I've gone through the quickstart and docs of Eask and most of the docs seem needless, since it still doesn't tell you how to start emacs with these dependencies. All I want to do is load emacs with my init.el configurations of the packages.
Running eask install-deps -c
throws errors:
Description cannot be an empty string
Package-file seems to be missing ‘.emacs.d.el’
Loading your configuration... Debugger entered--Lisp error: (void-function package-intialize)
(package-intialize)
eval-buffer(#<buffer *load*-973585> nil "~./.emacs.d/init.el" nil t) ; Reading at buffer position 296
load-with-code-conversion("~./.emacs.d/init.el" "~/.emacs.d/init.el" t nil)
#<subr load>("~/.emacs.d/init.el" t nil nil nil)
apply(#<subr load> ("~/.emacs.d/init.el" t))
(if (string= (nth 0 args) (eask-script "_prepare")) nil (apply fnc args))
eask--load--adv(#<subr load> "~/.emacs.d/init.el" t)
apply(eask--load--adv #<subr load> ("~/.emacs.d/init.el" t))
load("~/.emacs.d/init.el" t)
(if inhibit-config nil (load (l
Could you point me to the docs/readme on how to start Emacs with your Eask file?
Without this info, I don't understand the point of using Eask for developers using Emacs as an editor. I'm not interested in building Elisp libraries, and if that's the usecase you are supporting it should be articulated in your README.
Thank you.