Thanks for figuring this out. I'm now working on make check, and will
post a
new patch shortly (I hope).
The new patch is up at https://codereview.appspot.com/568650043
https://codereview.appspot.com/337870043/
___
lilypond-devel mailing
Hi Carl,
On 4/2/19 12:14 AM, carl.d.soren...@gmail.com wrote:
https://codereview.appspot.com/337870043/diff/40001/input/regression/chord-name-exceptions.ly#newcode29
input/regression/chord-name-exceptions.ly:29: chExceptions = #(append
(chordmode->exception-entry chordVar markupVar)
On 2018/11/10 05:44:23, pwm wrote:
https://codereview.appspot.com/337870043/diff/40001/Documentation/notation/chords.itely#newcode679
Documentation/notation/chords.itely:679: represent the structure of
the chord.
When entered in node mode,
typo: "note mode"
Done.
On 2018/11/10 19:44:47, pwm wrote:
Hi Charles, Today I built and ran 'make check' with your patch applied
to
current master. I was able to get it to pass 'make check' by making
the
following two changes.
1. In `chord-entry.scm` line 267, remove `(write-me "base3: " bass)`.
2. In that
Hi Charles, Today I built and ran 'make check' with your patch applied
to current master. I was able to get it to pass 'make check' by making
the following two changes.
1. In `chord-entry.scm` line 267, remove `(write-me "base3: " bass)`.
2. In that same file, line 100, remove the parens to
Hi Charles,
I was thinking about working on MusicXML export for chord symbols, and
wondered about the status of your GSOC project. (It would, of course,
make exporting chord symbols much simpler and more robust.) I was
really glad to find your code up on Reitveld, and was curious, so I gave
it
On 2018/08/12 13:54:08, lilypond-pkx wrote:
On 2018/08/11 14:59:10, chazwins6 wrote:
> Fixing errors in make doc.
Fails make check
input/regression/chord-names-languages.ly'
~~~
Parsing...
Renaming input to:
`/home/james/lilypond-git/input/regression/chord-names-languages.ly'
warning:
Hello Charles,
Thanks for your patch however, this fails make check.
It fails on a number of different reg tests but all with the same basic
error.
Example:
~~~
/home/james/lilypond-git/input/regression/chord-names-lower-case-minor.ly'
warning: cannot find property type-check for
On 2017/12/29 22:38:54, chazwins6 wrote:
Fixing errors with chord-semantics
This should be working now. Sorry for the delay, I was very busy with
school!
https://codereview.appspot.com/337870043/
___
lilypond-devel mailing list
Charles,
I just wanted to make sure you saw my last reply about your patch
failing the regression tests. It would be shame to let all your hard
work so far go to waste.
Regards
james
https://codereview.appspot.com/337870043/
___
lilypond-devel
Hello,
This fails a make check
Processing `./fd/lily-2f531b63.ly'
Parsing...
Renaming input to:
`/home/james/lilypond-git/input/regression/predefined-fretboards.ly'
warning: cannot find property type-check for `chord-semantics'
(music-type?). perhaps a typing error?
Writing timing to
11 matches
Mail list logo
