summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorMaxim Cournoyer <maxim.cournoyer@gmail.com>2019-08-27 19:36:05 +0900
committerMaxim Cournoyer <maxim.cournoyer@gmail.com>2019-08-27 19:36:05 +0900
commit4183105de08a2403915536a97d06ca0c119487bc (patch)
tree27298d0365c9e6decdc981f1d1e93ea43822fe21 /doc
parentd8f08344a7d6060fca73c12fe27a0d1a3528acda (diff)
downloadguix-4183105de08a2403915536a97d06ca0c119487bc.tar.gz
doc: Follow-up commit to 407ebeaa1.
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)".
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index c1e451fbec..6499b39ebf 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -12443,10 +12443,10 @@ gexps to introduce job definitions that are passed to mcron
 @end lisp
 
 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
-(macros), you can move your code to a separate program using the
-@code{program-file} procedure of the @code{(guix gexp)} module
-(@pxref{G-Expressions}).  The example below illustrates that.
+level, for instance to introduce a @code{use-modules} form, you can move your
+code to a separate program using the @code{program-file} procedure of the
+@code{(guix gexp)} module (@pxref{G-Expressions}).  The example below
+illustrates that.
 
 @lisp
 (define %battery-alert-job