aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2019-09-25 15:38:26 +0200
committerLudovic Courtès <ludo@gnu.org>2019-09-25 15:49:42 +0200
commit34e624a56ad42f93d8526f7c7e2025d26a4cba5e (patch)
treee6e8804ac785b80dab6cac6394d73503b922cb85 /doc
parent82b6bf8c0f05988305c126b5a6b196e1d57a19ea (diff)
downloadpatches-34e624a56ad42f93d8526f7c7e2025d26a4cba5e.tar
patches-34e624a56ad42f93d8526f7c7e2025d26a4cba5e.tar.gz
doc: Avoid @verbatiminclude for Scheme snippets.
* doc/guix.texi (Invoking guix package): Use @include instead of @verbatiminclude. (Additional Build Options): Likewise.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index dd54f7f747..267c2e9e6c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -2755,7 +2755,7 @@ As an example, @var{file} might contain a definition like this
(@pxref{Defining Packages}):
@lisp
-@verbatiminclude package-hello.scm
+@include package-hello.scm
@end lisp
Developers may find it useful to include such a @file{guix.scm} file
@@ -8231,7 +8231,7 @@ As an example, @var{file} might contain a package definition like this
(@pxref{Defining Packages}):
@lisp
-@verbatiminclude package-hello.scm
+@include package-hello.scm
@end lisp
@item --expression=@var{expr}