TakeV/guix
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

doc: Follow-up commit to 407ebeaa1.

Browse source 
Following some discussion with Ludovic (see:
https://lists.gnu.org/archive/html/guix-patches/2019-08/msg00506.html), it is
better advice to generally recommend the use of `program-file' for any usage
of modules, not just for those which define syntax.

* doc/guix.texi (Scheduled Job Execution): Drop the following text: "that
defines syntax (macros)".
This commit is contained in:
Maxim Cournoyer 2019-08-27 19:36:05 +09:00
parent d8f08344a7
commit 4183105de0
No known key found for this signature in database
GPG key ID: 1260E46482E63562
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/guix.texi
View file

@ -12443,10 +12443,10 @@ gexps to introduce job definitions that are passed to mcron
@end lisp @end lisp
For more complex jobs defined in Scheme where you need control over the top For more complex jobs defined in Scheme where you need control over the top
level, for instance to introduce a @code{use-modules} form that defines syntax level, for instance to introduce a @code{use-modules} form, you can move your
(macros), you can move your code to a separate program using the code to a separate program using the @code{program-file} procedure of the
@code{program-file} procedure of the @code{(guix gexp)} module @code{(guix gexp)} module (@pxref{G-Expressions}). The example below
(@pxref{G-Expressions}). The example below illustrates that. illustrates that.
@lisp @lisp
(define %battery-alert-job (define %battery-alert-job