gnuastro-commits
[Top][All Lists]
Advanced

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

[gnuastro-commits] master ea8f51bf: Book: added hashbang in the script o


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master ea8f51bf: Book: added hashbang in the script of the Sufi simulation tutorial
Date: Fri, 7 Oct 2022 12:22:13 -0400 (EDT)

branch: master
commit ea8f51bf913f01d64c4748495ecbd2df3b7c154d
Author: Faezeh Bijarchian <fbidjarchian@gmail.com>
Commit: Mohammad Akhlaghi <mohammad@akhlaghi.org>

    Book: added hashbang in the script of the Sufi simulation tutorial
    
    Until now, the details of writing a script weren't mentioned before the
    Sufi simulation tutorial. Therefore the example script at the end of that
    tutorial didn't have a hashband. After displacing the tutorials, the Sufi
    tutorial has come to the end. By this time, the reader has learned every
    detail about a script at the end of the general tutorial.  Therefore we can
    include details of a script's body!
    
    With this commit, the hashband "#!/bin/bash" has been added in the first
    line of the script to say the shell program to use is GNU Bash. Also a link
    to the script writing section of the general tutorial has also been added.
---
 doc/gnuastro.texi | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index 521838b3..4ecc9540 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -7439,10 +7439,12 @@ The command-line shell has the capability to read all 
the separate input command
 This is useful when you want to do the same thing multiple times, with only 
the names of the files or minor parameters changing between the different 
instances.
 Using the shell's history (by pressing the up keyboard key) Sufi reviewed all 
the commands and then he retrieved the last 5 commands with the @command{$ 
history 5} command.
 He selected all those lines he had input and put them in a text file named 
@file{mymock.sh}.
-Then he defined the @code{edge} and @code{base} shell variables for easier 
customization later.
-Finally, before every command, he added some comments (lines starting with 
@key{#}) for future readability.
+Then he defined the @code{edge} and @code{base} shell variables for easier 
customization later, and before every command, he added some comments (lines 
starting with @key{#}) for future readability.
+Finally, Sufi pointed the student to Gnuastro's @ref{General program usage 
tutorial}, which has a full section on @ref{Writing scripts to automate the 
steps}.
 
 @example
+#!/bin/bash
+
 edge=12
 base=cat
 



reply via email to

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