[Swift-commit] r6961 - SwiftTutorials/CIC_2013-08-09/doc

davidk at ci.uchicago.edu davidk at ci.uchicago.edu
Thu Aug 22 15:43:10 CDT 2013


Author: davidk
Date: 2013-08-22 15:43:10 -0500 (Thu, 22 Aug 2013)
New Revision: 6961

Modified:
   SwiftTutorials/CIC_2013-08-09/doc/README
Log:
Use cat -n rather than processing through source-highlighter for line numbering


Modified: SwiftTutorials/CIC_2013-08-09/doc/README
===================================================================
--- SwiftTutorials/CIC_2013-08-09/doc/README	2013-08-22 19:58:32 UTC (rev 6960)
+++ SwiftTutorials/CIC_2013-08-09/doc/README	2013-08-22 20:43:10 UTC (rev 6961)
@@ -158,9 +158,8 @@
 image:p1.png[]
 
 .p1.swift
-[source, txt]
 -----
-include::../part01/p1.swift[]
+sys::[cat -n ../part01/p1.swift]
 -----
 
 The sites.xml file included in each part directory gives Swift information about the machines we will be running on.
@@ -168,17 +167,17 @@
 below will tell Swift to run on the local machine only, and run just 1 task at a time.
 
 .sites.xml
-[source, txt]
 -----
-include::../part01/sites.xml[]
+sys::[cat -n ../part01/sites.xml]
 -----
 
 The app file translates from a Swift app function to the path of an executable on the file system. 
 In this case, it translates from "simulate" to simulate.sh and assumes that simulate.sh will 
 be available in your $PATH.
-[source, txt]
+
+.apps
 -----
-include::../part01/apps[]
+sys::[cat -n ../part01/apps]
 -----
 
 To run this script, run the following command:
@@ -207,9 +206,8 @@
 image:p2.png[]
 
 .p2.swift
-[source, txt]
 -----
-include::../part02/p2.swift[]
+sys::[cat -n ../part02/p2.swift]
 -----
 
 To run the script:
@@ -226,9 +224,8 @@
 image:p3.png[]
 
 .p3.swift
-[source, txt]
 ----
-include::../part03/p3.swift[]
+sys::[cat -n ../part03/p3.swift]
 ----
 
 To run:
@@ -247,9 +244,8 @@
 image:p4.png[]
 
 .p4.swift
-[source, txt]
 ----
-include::../part04/p4.swift[]
+sys::[cat -n ../part04/p4.swift]
 ----
 
 To run:
@@ -268,9 +264,8 @@
 image:p5.png[]
 
 .p5.swift
-[source, txt]
 ----
-include::../part05/p5.swift[]
+sys::[cat -n ../part05/p5.swift]
 ----
 
 To run:
@@ -286,25 +281,25 @@
 image:p6.png[]
 
 .p6.swift
-[source, txt]
 ----
-include::../part06/p6.swift[]
+sys::[cat -n ../part06/p6.swift]
 ----
 
 In order to run on the cluster, sites.xml needed to be modified. Here is 
 the new sites.xml we are using for this example. Note the changes between the sites.xml file
 in this example which uses condor, and the sites.xml file in part 1, which runs locally.
 
-[source, txt]
+.sites.xml
 -----
-include::../part06/sites.xml[]
+sys::[cat -n ../part06/sites.xml]
 -----
 
 Below is the updated apps file. Since Swift is staging shell scripts remotely to nodes on the cluster,
 the only application it needs defined here is the shell.
-[source, txt]
+
+.apps
 -----
-include::../part06/apps[]
+sys::[cat -n ../part06/apps]
 -----
 
 Use the command below to specify the time for each simulation.




More information about the Swift-commit mailing list