Skip to content

Commit

Permalink
docs: Mention that init-tangle target has to be run explicitly
Browse files Browse the repository at this point in the history
Closes #162.
  • Loading branch information
tarsius committed Aug 3, 2024
1 parent 91af0ee commit 2628c68
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 2 deletions.
7 changes: 6 additions & 1 deletion docs/borg.org
Original file line number Diff line number Diff line change
Expand Up @@ -748,7 +748,12 @@ those are the drones that take longer to build.
- Command: init-tangle ::

This target tangles (creates) ~init.el~ from ~init.org~. You obviously
don't have to use such a file if you don't want to.
don't have to use such a file, if you don't want to.

Note that this target is *not* a dependency of ~init-build~, because it
necessarily has to depend on ~init.org~, which for most people does
not exist. So you have to run this target explicitly after making
changes to ~init.org~.

- Command: init-build ::

Expand Down
7 changes: 6 additions & 1 deletion docs/borg.texi
Original file line number Diff line number Diff line change
Expand Up @@ -830,7 +830,12 @@ This target removes byte-code files for init files.

@deffn Command init-tangle
This target tangles (creates) @code{init.el} from @code{init.org}. You obviously
don't have to use such a file if you don't want to.
don't have to use such a file, if you don't want to.

Note that this target is @strong{not} a dependency of @code{init-build}, because it
necessarily has to depend on @code{init.org}, which for most people does
not exist. So you have to run this target explicitly after making
changes to @code{init.org}.
@end deffn

@deffn Command init-build
Expand Down

0 comments on commit 2628c68

Please sign in to comment.