I have successfully built my first #Emacs package. I want to clean it up a bit before I consider releasing it though. Also, while I can build a simple (single file) package, buildig a multi-file one is still eluding me.
When I try to install it, I get the following (less than helpful) error message:Wrong type argument: stringp, nil
Is there a way I can get more detail on why this is failing?
reshared this
vifon
in reply to Jonathan Lamothe • • •Jonathan Lamothe
in reply to Jonathan Lamothe • •So getting a stack trace doesn't seem to have provided any useful additional information, but I have a potential starting point. When I look at the auto-generated
*-pkg.elfile from the installed single file version, I notice that there are some additional parameters passed todefine-packagethat were not mentioned in the elisp documentation.I'll have to have a closer look later.
Shannon Prickett reshared this.
Jonathan Lamothe
in reply to Jonathan Lamothe • •To demonstrate that I'm not crazy, this is from section 42.3 of the elisp manual:
Function: define-package name version &optional docstring requirementsThis is from the documentation for
define-package:(define-package NAME-STRING VERSION-STRING &optional DOCSTRING REQUIREMENTS &rest EXTRA-PROPERTIES)🇺🇦 Myke
in reply to Jonathan Lamothe • • •Jonathan Lamothe
in reply to 🇺🇦 Myke • •@🇺🇦 Myke True enough, though I still want to know how to do it.
Plus, for larger projects it's sometimes easier to separate things out for clarity.
🇺🇦 Myke
in reply to Jonathan Lamothe • • •here’s a large project, still in one file:
github.com/protesilaos/denote
GitHub - protesilaos/denote: Simple notes for Emacs with an efficient file-naming scheme
GitHubJonathan Lamothe
in reply to 🇺🇦 Myke • •@🇺🇦 Myke Yes, it can be done that way as well.
That still doesn't negate the point that I want to know how to build a multi-file package.
Besides, sometimes I like to learn stuff just for the sake of learning it.