Open ghost opened 2 years ago
Yes, but I need to check the procedure.
Is there any way I can help with this?
Sorry for delay. If you have any pointer on the procedure and what needs to be done, that would be great.
@rougier, the MELPA package submission procedure can be found here. In short, you need to fork the MELPA repo, add a recipe for the package, then submit a pull request.
I'm trying to fix the pacakge before submission but I'm stuck with the make check
because of the async dependency. I'm not familiar with the Emacs Lisp Regression Testing and I'm not sure how to specify load path for async (and other packages). Any idea?
Here is how the Helm maintainer has solved this problem (lines 36 through 61). Locate the elpa/straight directory, find the async installation within that directory, add it to a LOAD_PATH variable (along with other paths that should be added to that variable, like the current directory), then load LOAD_PATH with emacs using the -L
option wherever emacs is called.
Thanks. I've one warning left: mu4e-dashboard.el:198:16: Warning: Unused lexical variable `mu4e-headers-results-limit'. Not sure how to get rid of it though.
I believe this is because the (local) variable mu4e-headers-results-limit
is not used within the let expression in which it is bound (line 198 of mu4e-dashboard.el) . I think this is a bug - I might be wrong, but I don't think you can temporarily change the value of a global variable within a let expression.
Incidentally, that variable has been marked as obsolete in the most recent mu release. The preferred alias of the variable is mu4e-search-results-limit
.
I might be wrong, but I don't think you can temporarily change the value of a global variable within a let expression.
You are incorrect. let-binding special variables is common practice.
To quell the byte-compiler (ignore mu4e-headers-results-limit)
can be added in the body of the let form.
Oops, sorry for the inaccuracy.
Done (no more lint warning). Need now to proceed with Melpa submission.
@rougier Is this still up?
In order to have reproducible builds and installs of Emacs, having a package distributed over MELPA would be lovely.
Would it be possible to package mu4e-dashboard as a melpa package?