damiencassou / emacs.d Goto Github PK

Hi Damien,

Forgive me for contacting you this way, but the registration page on makel's site says:

User registration is now closed due to spam. Please contact Nico to create an account.

Perhaps you would consider moving or mirroring the repo here so issues could be filed on it? :)

Anyway, I started using makel for https://github.com/alphapapa/ts.el, and I like it very much!

However, I've noticed that, by setting load-prefer-newer, it doesn't test byte-compiled versions of files if they haven't been compiled since being modified. Most of the time this doesn't matter, but in one of my other packages I found a difference in behavior when byte-compiled. It was minor, and I eventually resolved it with a simple change to the code, however it showed that it is good to test code in its byte-compiled form, since that's what most users will end up running.

So this means that my workflow should be something like:

1. Make changes to code.
2. Save .el file.
3. Byte-compile the file from within Emacs.
4. Run tests with makel.

If I forget step 3 (which I often do), the tests will run, but they will test the interpreted code rather than the byte-compiled code. And since makel's purpose is to make development easier and more reliable, it seems like it should handle step 3 for me. :)

What do you think? Could makel byte-compile the files before running tests?

I tried doing this myself by adding this to my Makefile:

.PHONY: test-compiled

test-compiled: lint-compile test-ert

Then I run make test-compiled, and it works, but it also lints, which I don't always want (e.g. I currently have the test.el file being byte-compiled, which works but raises a warning, which clutters the output).

It also seems like the test rule should test byte-compiled files by default, which I guess would require makel itself to be changed, so I wouldn't have to override the rule in my Makefile.

Thanks for your work!

I hope it is okay to reach out to you this way rather than via email.

I notice from your init.el you use the following packages:

• auth-source-pass (which you also developed)
• pass (which you have developed with Nicholas)
• password-store

And I see you have also contributed to password-store-otp though I could see no reference to it in your init.el. I'm in the process of changing all my passwords and the management of them and was curious if it was necessary to utilise all these packages to use pass from within Emacs.

I presume each package provides functionality not provided by the others. Is this the case?

With respect to your auth-source-pass I understand it is now included with Emacs. I'm currently using 26.3 so can I assume it has the latest version bundled with it?

Thanks for your time.

And Line 271.