2cellos

commit c4b0b3f553e0ea235a63fa5666c8255c57da3e95
parent 71a02d45f33dfa65b51adb98907071f384069bf1
Author: Jamie Beardslee <jdb@jamzattack.xyz>
Date:   Mon,  6 Jul 2020 03:05:34 +1200

Another directory sorting

cello-{1-2}.ly -> hurt-{1-2}.ly

I think this is tidier, because it actually uses descriptive
filenames.

Diffstat:
M
README.org
 | 
16
++++++++--------
M
hurt/Makefile
 | 
11
+++++++----
R
hurt/cello-1.ly -> hurt/hurt-1.ly
 | 
0

R
hurt/cello-2.ly -> hurt/hurt-2.ly
 | 
0

4 files changed, 15 insertions(+), 12 deletions(-)
diff --git a/README.org b/README.org
@@ -10,12 +10,12 @@ A piece will typically be laid out like so:
 └─hurt/
   ├─1.ly
   ├─2.ly
-  ├─cello-1.ly
-  ├─cello-1.midi
-  ├─cello-1.pdf
-  ├─cello-2.ly
-  ├─cello-2.midi
-  ├─cello-2.pdf
+  ├─hurt-1.ly
+  ├─hurt-1.midi
+  ├─hurt-1.pdf
+  ├─hurt-2.ly
+  ├─hurt-2.midi
+  ├─hurt-2.pdf
   ├─hurt.ly
   ├─hurt.midi
   ├─hurt.pdf
@@ -24,9 +24,9 @@ A piece will typically be laid out like so:
 
 Where:
 - =1.ly= and =2.ly= contain the actual music
-- =cello-1.ly= and =cello-2.ly= generate individual parts
+- =hurt-1.ly= and =hurt-2.ly= generate individual parts
 - =hurt.ly= generates the full score
-- =Makefile= contains entries for all the output files
+- =Makefile= contains recipes for all the output files
 
 * List of pieces
 
diff --git a/hurt/Makefile b/hurt/Makefile
@@ -1,10 +1,10 @@
 .PHONY: all
 .PHONY: clean
 
-LY = cello-1.ly cello-2.ly hurt.ly
+LY = hurt-1.ly hurt-2.ly hurt.ly
 PDF = ${LY:.ly=.pdf}
 
-hurt.pdf: 1.ly 2.ly hurt.ly
+hurt.pdf hurt.midi: 1.ly 2.ly hurt.ly
 	lilypond hurt.ly
 
 all: ${PDF}
@@ -12,5 +12,8 @@ all: ${PDF}
 clean:
 	rm *.pdf *.midi
 
-%.pdf %.midi: %.ly
-	lilypond $<
+hurt-1.pdf hurt-1.midi: hurt-1.ly 1.ly
+	lilypond hurt-1.ly
+
+hurt-2.pdf hurt-2.midi: hurt-2.ly 2.ly
+	lilypond hurt-2.ly
diff --git a/hurt/cello-1.ly b/hurt/hurt-1.ly
diff --git a/hurt/cello-2.ly b/hurt/hurt-2.ly