[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: polychords: a working solution
From: |
Thomas Morley |
Subject: |
Re: polychords: a working solution |
Date: |
Sat, 18 Feb 2012 16:05:36 +0100 |
Hi Phil,
2012/2/18 Phil Holmes <address@hidden>:
> I don't recall anyone asking for a volunteer. I'll do it.
so you are the man who volunteers for the LSR-task and so I adress to you:
> Users here for LSR update work.
I tried to find the LSR-snippets not compiling with the current stable
(2.14.2). Graham talked about 50 files.
I did the following (Contributors Guide 7.7 Updating LSR to a new version):
Download: lsr-snippets-all-2012-02-18.tar.gz (hope this is the correct one)
Run
convert-ly -e *.ly
on them (sometimes the log gave: Not smart enough ... )
Run:
#!/bin/bash
for LILYFILE in *.ly
do
STEM=$(basename "$LILYFILE" .ly)
echo "running $LILYFILE..."
lilypond --format=png -ddelete-intermediate-files "$LILYFILE" >& "$STEM".txt
done
grep failed *.txt
I got:
altering-the-number-of-stems-in-a-beam.txt:error: failed files:
"altering-the-number-of-stems-in-a-beam.ly"
automatic-beams-two-per-two-in-4-4-or-2-2-time-signature.txt:error:
failed files: "automatic-beams-two-per-two-in-4-4-or-2-2-time-signature.ly"
beam-endings-in-score-context.txt:error: failed files:
"beam-endings-in-score-context.ly"
beam-grouping-in-7-8-time.txt:error: failed files:
"beam-grouping-in-7-8-time.ly"
compound-time-signatures.txt:error: failed files: "compound-time-signatures.ly"
conducting-signs,-measure-grouping-signs.txt:error: failed files:
"conducting-signs,-measure-grouping-signs.ly"
filtering-parts-from-the-command-line.txt:error: failed files:
"filtering-parts-from-the-command-line.ly"
grouping-beats.txt:error: failed files: "grouping-beats.ly"
how-to-define-autobeamsettings-in-the--layout-block.txt:error: failed
files: "how-to-define-autobeamsettings-in-the--layout-block.ly"
including-a-file-only-once.txt:error: failed files:
"including-a-file-only-once.ly"
overriding-automatic-beam-settings.txt:error: failed files:
"overriding-automatic-beam-settings.ly"
reverting-default-beam-endings.txt:error: failed files:
"reverting-default-beam-endings.ly"
specifying-context-with-beatgrouping.txt:error: failed files:
"specifying-context-with-beatgrouping.ly"
template-for-multiple-instruments,-prints-a-score-and-parts.txt:error:
failed files: "template-for-multiple-instruments,-prints-a-score-and-parts.ly"
I repeated it with
grep ERROR *txt
with different result:
coloring-individual-staff-lines.txt:Drawing systems...ERROR: Unbound
variable: interval-translate
defining-predefined-fretboards-for-other-instruments.txt:Interpreting
music... ERROR: In procedure ly:pitch-semitones:
defining-predefined-fretboards-for-other-instruments.txt:ERROR: Wrong
type argument in position 1 (expecting Pitch): 9
letter-tablature-formatting.txt:Interpreting music... ERROR: In
procedure ly:context-property:
letter-tablature-formatting.txt:ERROR: Wrong type argument in position
1 (expecting Context): 5
mixed-meter---automatic-compound-time-signatures.txt:Interpreting
music... ERROR: Unbound variable: override-property-setting
obtaining-a-tablature-for-open-tuning-and-or-normal-tuning.txt:Interpreting
music... ERROR: In procedure ly:pitch-semitones:
obtaining-a-tablature-for-open-tuning-and-or-normal-tuning.txt:ERROR:
Wrong type argument in position 1 (expecting Pitch): 4
positioning-tuplet-numbers-close-to-kneed-beams.txt:Drawing
systems...ERROR: In procedure +:
positioning-tuplet-numbers-close-to-kneed-beams.txt:ERROR: Wrong type: ()
use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords.txt:Interpreting
music... ERROR: Wrong number of arguments to #<procedure
my-chord-name->pop-markup (pitch)>
Anyway, it seems to me that these are the files, which need manual
upgrade!? And less than 50.
Or did I sth wrong?
Cheers,
Harm
- Re: polychords: a working solution, (continued)
- Re: polychords: a working solution, James, 2012/02/17
- Re: polychords: a working solution, Phil Holmes, 2012/02/18
- Re: polychords: a working solution, Graham Percival, 2012/02/18
- Re: polychords: a working solution, Phil Holmes, 2012/02/18
- Re: polychords: a working solution, Graham Percival, 2012/02/18
- Re: polychords: a working solution, Phil Holmes, 2012/02/18
- Re: polychords: a working solution, Graham Percival, 2012/02/18
- Re: polychords: a working solution, Phil Holmes, 2012/02/18
- Re: polychords: a working solution,
Thomas Morley <=
- Re: polychords: a working solution, Thomas Morley, 2012/02/18
- Re: polychords: a working solution, David Kastrup, 2012/02/18
- Re: polychords: a working solution, Phil Holmes, 2012/02/18
- Re: polychords: a working solution, Thomas Morley, 2012/02/18
- Re: polychords: a working solution, Graham Percival, 2012/02/18
- Re: LSR updates: was: polychords: a working solution, Phil Holmes, 2012/02/19
- Re: LSR updates: was: polychords: a working solution, David Nalesnik, 2012/02/19
- Re: LSR updates: was: polychords: a working solution, Jean-Alexis Montignies, 2012/02/19
- Re: LSR updates: was: polychords: a working solution, Thomas Morley, 2012/02/19
- Re: LSR updates: was: polychords: a working solution, David Kastrup, 2012/02/19