el-get/recipes/mu4e.rcp
Fr. John Jenkins c11d12a176
Update mu4e.rcp (#2903)
The build directory actually contains the finished product which are never moved out of that directory. You cannot load mu4e until you point the load-path to the build directory first. An alternative work around is to specify this parameter: (el-get-bundle mu4e :load-path "build/mu4e")
2023-06-11 20:30:52 +02:00

18 lines
680 B
Plaintext

(:name mu4e
:website "http://www.djcbsoftware.nl/code/mu/mu4e.html"
:description "An emacs-based e-mail client which uses mu (http://www.djcbsoftware.nl/code/mu/) as its back-end: mu4e."
:type github
:pkgname "djcb/mu"
:post-init (setq mu4e-mu-binary
;; "el-get-dir/mu4e/mu/mu"
(expand-file-name
"mu"
(expand-file-name
"mu"
(el-get-package-directory 'mu4e))))
:build `(("./autogen.sh")
("make"))
:load-path "build/mu4e"
:info "build/mu4e/mu4e.info"
)