cmark

My personal build of CMark ✏️

Commit: 3643c9c36b35bdd2b5da963ac3d05ef0e2cbf7e7
Parent: d76f07909ff44a36b0ea6e993484ad9e9fd6ff11
Author: John MacFarlane <jgm@berkeley.edu>
Date: Sat, 29 Nov 2014 21:36:22 -0800

Updated path for spec_test.py.

Diffstat

2 files changed, 3 insertions, 3 deletions

Status	File Name	N° Changes	Insertions	Deletions
Modified	README.md	4	2	2
Modified	spec.txt	2	1	1

diff --git a/README.md b/README.md
@@ -75,12 +75,12 @@ Or, to create Xcode project files on OSX:
 
 Tests can also be run manually on any executable `$PROG` using:
 
-    python spec_tests.py --program $PROG
+    python test/spec_tests.py --program $PROG
 
 If you want to extract the raw test data from the spec without
 actually running the tests, you can do:
 
-    python spec_tests.py --dump-tests
+    python test/spec_tests.py --dump-tests
 
 and you'll get all the tests in JSON format.

diff --git a/spec.txt b/spec.txt
@@ -173,7 +173,7 @@ HTML.  These are intended to double as conformance tests.  An
 accompanying script `spec_tests.py` can be used to run the tests
 against any Markdown program:
 
-    python spec_tests.py --spec spec.txt --program PROGRAM
+    python test/spec_tests.py --spec spec.txt --program PROGRAM
 
 Since this document describes how Markdown is to be parsed into
 an abstract syntax tree, it would have made sense to use an abstract