Reasons somebody may have misspelled a word: glitchy phone screen, non-native english speaker, they expected their spellchecker to fix it and it failed, dyslexia, standardised spelling is a fake invention of the printing press industry to sell more moveable type
Reasons somebody my have substituted a homophone (eg their and there): Their dictation software fucked up, their spell checker fucked up, they're a non-native english speaker, they were thinking verbally, standardised spelling is a fake invention of the printing press industry to sell more moveable type.
Reasons somebody may have put in the wrong word: Their spellchecker did a substitution and they didn’t notice, their dictation software fucked up, they speak a different English dialect in which that word was correct, they were editing the sentence and made a mistake.
Syntax errors very rarely indicate unclear thinking. They're just typos. It's the logic errors that fuck everything up. Anybody judging the value of an argument based on syntax is missing the more important picture: the printing press companies have lead us down an evil path, but its not to layt too eskayp
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.