Timeline for How do I require a package installed via .cask in a project
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2018 at 18:24 | vote | accept | indigo0086 | ||
| Mar 29, 2018 at 18:24 | vote | accept | indigo0086 | ||
| Mar 29, 2018 at 18:24 | |||||
| Mar 29, 2018 at 18:12 | answer | added | ebpa | timeline score: 2 | |
| Mar 29, 2018 at 17:32 | comment | added | indigo0086 | How do i mark your answer as the appropriate one @ebpa , can't seem to do that with comments? | |
| Mar 29, 2018 at 15:16 | comment | added | indigo0086 | Thanks, I got it working with cask emacs and will look at flycheck-cask. | |
| Mar 29, 2018 at 15:10 | comment | added | ebpa |
My workflow for package development is to independently install all package dependencies like that using package-install (ex: M-x package-install buttercup). You will probably discover though that buttercup is not written with an interactive use of buttercup in mind. I would recommend using cask exec (ex: cask exec buttercup -L .) to invoke buttercup so you can be confident that dependencies for your tests are properly expressed for cask.
|
|
| Mar 29, 2018 at 14:44 | comment | added | indigo0086 |
So in my case I cloned the cider project github.com/clojure-emacs/cider. Downloaded and ran cask install and I see the .cask folder. I open up the test and try to eval the (require 'buttercup) expression and it just says cannot open load file: no such file or directory, buttercup. This is mainly so I can develop with the proper indentation as that is attached to the defs of buttercup. Otherwise the indentation is the standard lisp for function calls which aligns arguments.
|
|
| Mar 29, 2018 at 13:08 | comment | added | ebpa |
If the package has its dependencies properly declared,cask install should do all the setup that is necessary. Cask then builds the load-path automatically for you so that (require ...) statements resolve when you invoke cask exec. You may need to further illustrate your circumstances, to clarify how things are not as you expect. Are you interactively working on the package within emacs? You might try starting emacs using cask emacs from within the package directory to have the desired load-path or reading though github.com/cask/cask/issues/360.
|
|
| Mar 29, 2018 at 1:31 | history | asked | indigo0086 | CC BY-SA 3.0 |