[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] 01/02: "Scripting Examples" update.

From: Andy Wingo
Subject: [Guile-commits] 01/02: "Scripting Examples" update.
Date: Tue, 28 Feb 2017 11:03:47 -0500 (EST)

wingo pushed a commit to branch master
in repository guile.

commit f3a1872703bf8b9b8f92bbdba01aa75927bd1b8f
Author: Andy Wingo <address@hidden>
Date:   Tue Feb 28 16:22:42 2017 +0100

    "Scripting Examples" update.
    * doc/ref/scheme-scripts.texi (Scripting Examples): Mention system* and
 doc/ref/scheme-scripts.texi | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/doc/ref/scheme-scripts.texi b/doc/ref/scheme-scripts.texi
index 7552dba..296bea7 100644
--- a/doc/ref/scheme-scripts.texi
+++ b/doc/ref/scheme-scripts.texi
@@ -402,6 +402,17 @@ $ ./choose 50 100
 @end example
+Finally, seasoned scripters are probably missing a mention of
+subprocesses.  In Bash, for example, most shell scripts run other
+programs like @code{sed} or the like to do the actual work.
+In Guile it's often possible get everything done within Guile itself, so
+do give that a try first.  But if you just need to run a program and
+wait for it to finish, use @code{system*}.  If you need to run a
+sub-program and capture its output, or give it input, use
address@hidden  @xref{Processes}, and @xref{Pipes}, for more
 @c Local Variables:
 @c TeX-master: "guile.texi"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]