Matt - that's not really the problem. In general, these core org-cite functions (org-cite-make-insert-processor and org-cite-register-processor) must be loaded after anything they refer to; e.g. placed at the end of the package file.
But if they aren't, the resulting error message is really confusing, and emacs shouldn't break. On Thu, Jul 22, 2021 at 9:27 AM Matt Price <mopto...@gmail.com> wrote: > > Bruce, are you loading this code with use-package? If so, and if I'm reading > this right, you can perhaps add the missing functions to the > > :commands > > directive for org-mode? IIUC that should ensure that they are available to > your package, as long as you have an > :after (org oc) > line in the package's use-package directive. > > On Thu, Jul 22, 2021 at 6:31 AM Bruce D'Arcus <bdar...@gmail.com> wrote: >> >> The problem was load order I guess; putting this of the file fixes it. >> >> So when org-citemake-insert-processor is first loaded, it looks for >> the two functions, which haven't been loaded yet. >> >> I still think a) the error message could say that (that the functions >> aren't found or some such), and b) that it shouldn't break starting >> Emacs. >> >> On Thu, Jul 22, 2021 at 4:27 AM Bruce D'Arcus <bdar...@gmail.com> wrote: >> >> > If I comment out those lines and use the oc-basic style selector >> > instead to start emacs, and from there reactivate this function and >> > compile and reload the code from the buffer, THEN it works without >> > error. >>