:tangle no produces a weird tangling behavior #32
Labels
No Label
⭐.
duplicate
good luck!
help
help wanted
idea
invalid
it's not me
nope
question
uh-oh
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tec/emacs-config#32
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello, and thanks a lot for making your amazing config this readable and friendly :)
I am learning a lot but I am still struggling on the "Systemd daemon" part with no success.
Although I understood how you leveraged the org-mode literate programming powers, I noticed a weird behavior with a source block:
Basically, this one tangles
systemctl --user enable emacs.service
tosetup.sh
only if the service is not already enabled, and that works well to createsetup.sh
the first time.But then, when I save my
config.org
after an edit and look atconfig.el
, this very code block was tangled to:and the "
-
" causes a(void-variable -)
error at the next reboot.Note: I have not incorporated your "Asynchronous config tangling" part.
Strangely, when I run
doom sync
, the tangling of this block becomes:Do you have any idea why and how it could be avoided?
If so, could you please demystify this for me? :)
Frankly, I'm not sure what's going on there. I haven't ever seen this with my own setup.