Eager macro-expansion failure: (file-missing "Opening input file" "No such file or directory"

[danielkrajnik]

Trying it on doom emacs, GNU Emacs 29.1, but running systemd-mode in a buffer gives an error:

File mode specification error: (error Eager macro-expansion failure: (file-missing "Opening input file" "No such file or directory" "/home/user/.config/emacs/.local/straight/build-29.1/systemd-mode/unit-directives.txt"))

[simonsjw]

Same on vanilla emacs (different loadpath due to package management differences).

Fix was to copy in the unit-directives.txt nspawn-directives.txt and network-directives.txt files to that location.

[deirn]

With doom emacs the fix was to also include the directives text:

(package! systemd-mode :recipe (:files ("*.el" "*directives.txt")))

[dadinn]

This problem still exists also when using straight. The recipe there is correct, and symlink all the .txt files under the build directory.

Yet the error still prevails.

[dcunited001]

https://www.youtube.com/watch?v=N5O3rr65Qu4

(nothing personal... it's just sad)

[dcunited001]

I haven't looked at this in a while, but I understand straight & emacs lisp a bit better now.

On first glance, running M-x straight-rebuild-package with systemd-mode doesn't seem to show errors.

The symbols are created with def-const, but the error is being thrown at runtime -- it's not being compiled on Doom Emacs (or it's not loading the compiled native code.

From this r/vim post, there's a suggestion to extract keywords. It's stated is also how povini.vim and gitconfig.vim work.

The difficulty in maintaining this package is that you need a partial build of systemd to generate the txt files. I didn't look long, but this file is iterated as a template across different systemdingies or, technically speaking: different types of unit-thing-timer-fdsafdsa -- i'm very frustrated with how opaque systemd is, considering how essential and ubiquitous it is.

Anyways, I can look into it, but this has been on multiple TODO lists for about 3 years, more or less. maybe I can fork/maintain it or create a new one

again, nothing personal to the author. open source is a lot of work & mostly volunteer. it's usually an opening for someone else to help and if no one does, then it doesn't get done. there's no reason to complain much. my grip is with the systemd ecosystem as a whole: the man docs are scattered and send you in loops, there no concise information on which commands support json & which don't.

you're just expected to show up at some esoteric initiation certification class.

[dcunited001]

From what I remember, the big benefit to systemd-mode was not the syntax highlighting. It's the documentation functionality.

Otherwise, conf-mode pretty much covers systemd files.

As for getting this to work, you can just unload the systemd-mode from auto-mode-alist or prevent it from loading in Doom Emacs or whatever.

The other one that's sad to see being difficult to use is dcunited001/syslog-mode which includes a strace log viewer. idk what other tools to use to grok these, but there's one line to change in here that gets it partially functioning.

[dcunited001]

The project expects you to run make all. It generates the systemd.elc file, so it's not directly compatible with straight's build process.

Specifying (:pre-build ("make" "all") :build (autoloads compile)) in the straight recipe fixes the problem.

(package! systemd-mode
  ;; :build (autoloads compile native-compile info)
  :recipe 
  ;; idk whether fully specifying :type, :host, :repo makes a difference
  ;; for doom's fetch/build. 
  (:type git :host github :repo "holomorph/systemd-mode" 
  :files (:defaults)
  :pre-build ("make" "all")
   ;; adding native-compile here didn't produce *.eln
  :build (autoloads compile native-compile)))

M-x doom-reload-packages reloads package definitions in packages.el, so you don't need to restart the server (I can't get doom build or whatever to simply build one package.)

Similar works for other ways to install straight packages. However, for Doom Emacs, it's building this into the $EMACSDIR/.local/straight/repos/systemd-mode directory and symlinking systemd.el from $EMACSDIR/.local/straight/repos/systemd-mode, so there's no way to get use-package to load it (that I know of).

IDK enough about the emacs build system(s) to troubleshoot much.

You can (require 'systemd (expand-file-name ".local/straight/repos/systemd-mode/systemd.elc" doom-emacs-dir)) if you find the path to the file that straight built