Patch is fixed:
http://www.apollinemike.com/lilypond/waveform/0002-Waveform.patch
Could someone please throw it up on Reitveld?
As for the translation, I'm talking about language translators. I'm not
sure if the strings in my programming_errors are sufficiently clear to be
translateable - I
Move to font.scm or backend-library.scm?
Moved to backend-library.scm. I mistook output-lib to be the
library for output-*.scm but it isn't, thanks.
http://codereview.appspot.com/1428042/show
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 2010/06/06 18:42:05, Patrick McCarty wrote:
http://codereview.appspot.com/1428042/diff/13002/17014
File configure.in (right):
http://codereview.appspot.com/1428042/diff/13002/17014#newcode140
configure.in:140: STEPMAKE_PATH_PROG(FONTFORGE, fontforge, REQUIRED,
20090923)
Is 20090923
Em 06/06/10 23:41, Han-Wen Nienhuys escreveu:
[+lily-devel]
The list is probably a better place to ask around.
On Sun, Jun 6, 2010 at 3:53 PM, Frans van Dunnéfr...@southshield.net wrote:
Dear Han Wen,
I made a preliminary syntax colouring xml available to use BBedit or
TextWrangler
In section 2.2.5 TextMate of the Application Usage documentation,
the command for installing the TextMate bundle is given as:
svn co http://macromates.com/svn/Bundles/trunk/Bundles/Lilypond.tmbundle/
That is currently incorrect and will result in a redirection statement
which then results in an
On Mon, Jun 7, 2010 at 2:49 PM, Phillip Koebbe phillipkoe...@gmail.com wrote:
In section 2.2.5 TextMate of the Application Usage documentation,
Thanks for this report, but that section has been removed from the
2.13 docs; information about editors will be accessed through the
Easier Editing web
in the enumeration of paper block variables top-system-spacing is mentioned
twice.
--
View this message in context:
http://old.nabble.com/typo-in-NR-4.4.2-Vertical-spacing-between-systems-tp28805958p28805958.html
Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com.
Thanks, I'll check this and make a patch.
James
-Eluze wrote:
in the enumeration of paper block variables top-system-spacing is mentioned
twice.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Patch has been applied.
Thanks Eluze.
James
James Lowe wrote:
Thanks, I'll check this and make a patch.
James
-Eluze wrote:
in the enumeration of paper block variables top-system-spacing is
mentioned
twice.
___
lilypond-devel mailing list
Hi Jan,
I've just been testing this patch, and have stumbled upon a problem with
chords. With this snippet,
\chords {
c4
}
I get the following error message:
/home/neil/lilypond/out/share/lilypond/current/scm/backend-library.scm:270:23:
In procedure car in expression (car
On 6/6/10 8:01 AM, Graham Percival gra...@percival-music.ca wrote:
I'm seeing too much juggling. Focus on the Regressions -- dump
all other info into the CG (anywhere that makes remote sense,
other than CG 1, 2, and 7). Don't bother with a patch-review for
that info-dump. Then work
Hi Jan,
Have you checked what happens with full-bar rests?
I haven't tested your patch, but it's similar to the one I posted, which
suffers from invisible tempo marks at full-bar rests.
Cheers,
Neil
http://codereview.appspot.com/1579041/diff/2001/3001
File lily/metronome-engraver.cc (right):
On 2010/06/07 13:59:45, Reinhold wrote:
The only occurrence where it might make sense to have a separate
parser is in
scm/parser-ly-from-scheme.scm in the function read-lily-expression,
which calls
parse-string-result. However, I fail to see where this is actually
used...
It's called
On 2010/06/07 19:17:27, Neil Puttock wrote:
On 2010/06/07 13:59:45, Reinhold wrote:
However, I fail to see where this is actually used...
It's called whenever Guile encounters the character sequence #{ for
parsing
LilyPond expressions inside scheme (i.e., inside music functions).
Ah,
Looks nicely done to me. It was a big job!
Thanks,
Carl
http://codereview.appspot.com/1543042/show
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 6 June 2010 09:51, Benkő Pál benko@gmail.com wrote:
attached the updated patch for 1082.
Thanks, applied.
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Op maandag 07-06-2010 om 16:59 uur [tijdzone +], schreef
n.putt...@gmail.com:
Hi Neil,
Have you checked what happens with full-bar rests?
Uhuh, I have now ;-)
I haven't tested your patch, but it's similar to the one I posted, which
suffers from invisible tempo marks at full-bar rests.
17 matches
Mail list logo
