Closed sirikid closed 4 years ago
I agree the message is bad, but I have no idea how you got it. Please provide at least the command that you used ($ eldev foo ...
) and ideally also the package, e.g. GitHub URL if it is public.
This message comes from Emacs itself, so I cannot really change it. However, Eldev now adds some hints to it, hopefully making it less confusing.
Thanks!
Error message:
No .el files with package headers in ‘/.../’
But checkdoc passes just fine, the cause was the version field. I've added all the required keywords from the info, if eldev requires more than that, it would be useful to have better error messages and/or a separate checker.