Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Comment #23 on issue 1349 by ianhuli...@gmail.com: Guile 2.0 compat: Scheme
macros must be defined/autocompiled before they are used.
http://code.google.com/p/lilypond/issues/detail?id=1349
Hi Graham,
I would push the patch myself, but I can't get the ssh connection to
Savannah to work :-{.
I followed the instructions from the CG you sent re git push access.
I've tried generating and using both dsa and rsa public keys, and
entering them on the Savannah My Account/Account Configuration page,
but I still can't get git pull --verbose to work. This is frustrating -
gr...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
Am Saturday, 20. August 2011, 06:25:26 schrieben Sie:
> Comment #41 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
> http://code.google.com/p/lilypond/issues/detail?id=1691
>
> Trevor reminded us (by email) that lilypond automatically sets
> ragged-right=##t if the music is less than a full line. This might be the
> behavior Reinhold was seeing. If he was seeing it in a different context,
> then this sounds like another bug. There's no reason why relative=1 should
> imply ragged-right.
No, it was not the implicit ragged setting for one-line snippets. Rather, the
snippets' ly files have an exmplicit
ragged-right=##t
inserted.
The issue is that the relative snippet option implies the fragment option,
which seems to set the ragged-right=##t in all its snippets...
Attached is a simple example to show this, using three snippets with identical
contents, but different snippet options. The first snippet will not have
ragged-right, but the other two will get an explicit ragged-right=##t in the
snippet's .ly file. While this behavior is indirectly explained in the AU, it
does not really make sense from a user's standpoint that relative should
automatically imply ragged-right (having "fragment" imply ragged-right makes
sense to make it easier for documentation writers)
This deserves a bug report on its own.
To be honest, the whole snippet option handling seems to be a real mess right
now. I'll probably take a look at the whole snippet options handling system in
lilypond-book during the next few days. Probably we can properly analyze each
option's effects and make them more predictable (and correct).
Cheers,
Reinhold
--
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
@setfilename LineTest
@settitle PhilTest
@letterpaper
still problem:
@lilypond[]
\repeat unfold 50 { c'4 }
@end lilypond
@lilypond[fragment]
\repeat unfold 50 { c'4 }
@end lilypond
@lilypond[relative=1]
\repeat unfold 50 { c4 }
@end lilypond
@bye___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines.
Updates: Status: Verified Comment #12 on issue 1673 by lilyli...@googlemail.com: patch Allows glissandi to span multiple lines. http://code.google.com/p/lilypond/issues/detail?id=1673 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
On Sat, Aug 20, 2011 at 01:18:23PM +0200, Reinhold Kainhofer wrote:
> While this behavior is indirectly explained in the AU, it
> does not really make sense from a user's standpoint that relative should
> automatically imply ragged-right (having "fragment" imply ragged-right makes
> sense to make it easier for documentation writers)
[fragment] is either discouraged or forbidden in the docs. With
the docs doing auto-ragged-right for short ones, and in any case
it's easy enough to add [ragged-right] if you really want.
We should remove that behavior. [fragment] should simply add the
{...} container; nothing more, nothing less.
> To be honest, the whole snippet option handling seems to be a real mess right
> now. I'll probably take a look at the whole snippet options handling system
> in
> lilypond-book during the next few days. Probably we can properly analyze each
> option's effects and make them more predictable (and correct).
That would be great!
Cheers,
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR3.2.2: erroneous example?
Le 20/08/2011 00:03, Trevor Daniels disait :
Jean-Charles, you wrote Friday, August 19, 2011 3:02 PM
Since the only header fields that will be printed are piece and opus,
the example in "Custom text formatting for title blocks" should read
(line 802 of input.itely)
- subtitle = \markup { \italic "(Excerpt)" }
+ opus = \markup { \italic "(Excerpt)" }
May I change it myself, or?
Please do.
OK
When this section was changed quite a lot
of useful information was lost. I think
the following also needs to be reinserted
(properly formatted, of course) in Title
blocks explained:
Since I don't like very much having two consecutive
"if" sentences, I would favor:
-
If the book only has a single score, the @code{\header} block may be
placed inside or outside of the @code{\score} block.
The default behavior, when the @code{\header} has been defined inside
the @code{\score} block, is to print only the @code{piece} and @code{opus}
fields:
@lilypond[papersize=a5,quote,verbatim,noragged-right]
\score {
{ c'4 }
\header {
title = "title" % not printed
piece = "piece"
opus = "opus"
}
}
@end lilypond
@funindex print-all-headers
@noindent
You may change this behavior (and print all the headers when defining
@code{\header} inside @code{\score}) by using
@example
\paper@{
print-all-headers = ##t
@}
@end example
@warning{Remember when adding a @bs{}@code{header} block inside a
-
Cheer,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR3.2.2: erroneous example?
Jean-Charles, you wrote
Since I don't like very much having two consecutive
"if" sentences, I would favor:
-
If the book only has a single score, the @code{\header} block may
be
placed inside or outside of the @code{\score} block.
The default behavior, when the @code{\header} has been defined
inside
the @code{\score} block, is to print only the @code{piece} and
@code{opus}
fields:
@lilypond[papersize=a5,quote,verbatim,noragged-right]
\score {
{ c'4 }
\header {
title = "title" % not printed
piece = "piece"
opus = "opus"
}
}
@end lilypond
@funindex print-all-headers
@noindent
You may change this behavior (and print all the headers when
defining
@code{\header} inside @code{\score}) by using
@example
\paper@{
print-all-headers = ##t
@}
@end example
@warning{Remember when adding a @bs{}@code{header} block inside a
-
I like it! Thanks for picking this up!
Trevor
-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3845 - Release Date: 08/19/11
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR3.2.2: erroneous example?
Le 20/08/2011 16:11, Trevor Daniels disait : I like it! Thanks for picking this up! Done as 6810d727b278d15825eecb2b497d1a966241d4eb Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
Am Friday, 19. August 2011, 23:06:36 schrieb Trevor Daniels: > Are you sure relative=1 sets ragged-right? > That would be silly. But ragged-right is set by > LilyPond if there is only one system in the output. > This seems quite sensible. Yes, relative=1 implies fragment, which on the other hand implies ragged-right (see also the docs for lilypond-book). This made sense when single-line files in lilypond didn't automatically switch to ragged-right. But now this fallback (fragmend implying ragged-right to prevent stretching for simple snippets) is no longer needed... Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
42 issues changed in lilypond
Updates: Labels: -Maintainability Type-Maintainability Comment by percival.music.ca: (No comment was entered for this change.) Affected issues: issue 777: python script for indenting lilypond files http://code.google.com/p/lilypond/issues/detail?id=777 issue 788: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 issue 804: Code cleaning: checking types-conversion issues and other build warnings http://code.google.com/p/lilypond/issues/detail?id=804 issue 814: warning-as-error should be enabled when compiling the regtests http://code.google.com/p/lilypond/issues/detail?id=814 issue 847: python scripts should add an autogenerated marker http://code.google.com/p/lilypond/issues/detail?id=847 issue 848: news-front for general.itexi should be auto-geneated http://code.google.com/p/lilypond/issues/detail?id=848 issue 853: use .ily for "setup" input files http://code.google.com/p/lilypond/issues/detail?id=853 issue 858: automatically update version numbers in general.texi http://code.google.com/p/lilypond/issues/detail?id=858 issue 869: input/regression/ renaming to regression/ http://code.google.com/p/lilypond/issues/detail?id=869 issue 933: automatic, daily out-of-build tests http://code.google.com/p/lilypond/issues/detail?id=933 issue 938: building lilypond omf files: what, why, how, etc http://code.google.com/p/lilypond/issues/detail?id=938 issue 940: unify announcement methods http://code.google.com/p/lilypond/issues/detail?id=940 issue 979: waf build system http://code.google.com/p/lilypond/issues/detail?id=979 issue 980: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 issue 1000: send texi2html patches upstream http://code.google.com/p/lilypond/issues/detail?id=1000 issue 1015: doc line width http://code.google.com/p/lilypond/issues/detail?id=1015 issue 1034: Documentation: categorizing music-function docstrings http://code.google.com/p/lilypond/issues/detail?id=1034 issue 1040: regtest for changing file names http://code.google.com/p/lilypond/issues/detail?id=1040 issue 1050: website translations should use gettext http://code.google.com/p/lilypond/issues/detail?id=1050 issue 1055: guile 2.0 http://code.google.com/p/lilypond/issues/detail?id=1055 issue 1184: easier rietveld patches http://code.google.com/p/lilypond/issues/detail?id=1184 issue 1217: clean up undocumented regtests in 2.14.0. http://code.google.com/p/lilypond/issues/detail?id=1217 issue 1236: CG+scripts should use ~/lilypond-git/ http://code.google.com/p/lilypond/issues/detail?id=1236 issue 1349: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 issue 1370: any console-output-producing regtests should be separate http://code.google.com/p/lilypond/issues/detail?id=1370 issue 1387: Enhancement: discuss whether non-trivial convert-ly should trace as a comment in .ly files http://code.google.com/p/lilypond/issues/detail?id=1387 issue 1397: translators might want to run convert-ly manually http://code.google.com/p/lilypond/issues/detail?id=1397 issue 1413: add ly_display_scm to CG http://code.google.com/p/lilypond/issues/detail?id=1413 issue 1417: regtests "time" field is broken http://code.google.com/p/lilypond/issues/detail?id=1417 issue 1418: regtests "cells:" field isn't documented in the CG http://code.google.com/p/lilypond/issues/detail?id=1418 issue 1477: suppress output for expected warnings http://code.google.com/p/lilypond/issues/detail?id=1477 issue 1526: Building only English docs http://code.google.com/p/lilypond/issues/detail?id=1526 issue 1529: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 issue 1592: regtest for midi output http://code.google.com/p/lilypond/issues/detail?id=1592 issue 1595: lilypond-book papersize gives margin warnings http://code.google.com/p/lilypond/issues/detail?id=1595 issue 1638: lilypond-book [quote] hard-codes 5\in http://code.google.com/p/lilypond/issues/detail?id=1638 issue 1686: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available http://code.google.com/p/lilypond/issues/detail?id=1686 issue 1690: old announcements+changes on website http://code.google.com/p/lilypond/issues/detail?id=1690 issue 1707: add python -tt to build system http://code.google.com/p/lilypond/issues/detail?id=1707 issue 1780: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 issue 1797: fixcc.py should warn about astyle version http://code.google
Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated
Updates: Labels: Type-Enhancement Comment #3 on issue 1826 by percival.music.ca: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated http://code.google.com/p/lilypond/issues/detail?id=1826 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 380 in lilypond: cycling markup reference segfaults
Updates: Owner: --- Labels: -Type-Defect -Priority-Postponed Type-Crash Comment #13 on issue 380 by percival.music.ca: cycling markup reference segfaults http://code.google.com/p/lilypond/issues/detail?id=380 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken
Updates: Status: Fixed Comment #4 on issue 1295 by percival.music.ca: Support for Mac OSX 10.3.9 "Panther" is broken http://code.google.com/p/lilypond/issues/detail?id=1295 Since we officially do not support 10.3.9, and there is no movement to add that support back in, I'm closing this. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
70 issues changed in lilypond
Updates: Labels: -type-Collision Type-Ugly Comment by percival.music.ca: (No comment was entered for this change.) Affected issues: issue 22: collision tuplet number and staff with increased spacing http://code.google.com/p/lilypond/issues/detail?id=22 issue 39: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 issue 40: collision glissando accidental (includes workaround) http://code.google.com/p/lilypond/issues/detail?id=40 issue 155: \parenthesize does not take accidentals into account http://code.google.com/p/lilypond/issues/detail?id=155 issue 220: fingering too close to previous note http://code.google.com/p/lilypond/issues/detail?id=220 issue 257: collision accent and tuplet bracket http://code.google.com/p/lilypond/issues/detail?id=257 issue 304: Slurs and phrasing slurs should not collide at endpoints http://code.google.com/p/lilypond/issues/detail?id=304 issue 307: collision slur with tuplet bracket http://code.google.com/p/lilypond/issues/detail?id=307 issue 376: tremolo beams can collide with notes http://code.google.com/p/lilypond/issues/detail?id=376 issue 397: collision pitchedTrill and tie http://code.google.com/p/lilypond/issues/detail?id=397 issue 427: ugly collision slur and phrasing slur http://code.google.com/p/lilypond/issues/detail?id=427 issue 428: collision avoidance fails sometimes with simultaneous voices http://code.google.com/p/lilypond/issues/detail?id=428 issue 439: script collides with cross-staff beam http://code.google.com/p/lilypond/issues/detail?id=439 issue 472: collision rest + (accidental/notehead) with beaming http://code.google.com/p/lilypond/issues/detail?id=472 issue 480: collision: tie after line break with sharp/natural accidental http://code.google.com/p/lilypond/issues/detail?id=480 issue 509: collision nested tuplet numbers http://code.google.com/p/lilypond/issues/detail?id=509 issue 523: grace note forces tremolo above whole note http://code.google.com/p/lilypond/issues/detail?id=523 issue 570: Articulations can collide with ties http://code.google.com/p/lilypond/issues/detail?id=570 issue 586: Cross-staff slur causes a weird output http://code.google.com/p/lilypond/issues/detail?id=586 issue 590: Ties can collide with augmentation dots http://code.google.com/p/lilypond/issues/detail?id=590 issue 601: Accidentals cause cross-staff or cross-voice arpeggio collisions http://code.google.com/p/lilypond/issues/detail?id=601 issue 621: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc) http://code.google.com/p/lilypond/issues/detail?id=621 issue 646: Collision note/clef due to translated markup http://code.google.com/p/lilypond/issues/detail?id=646 issue 696: Misplaced tuplet number collides with accidental when a kneed beam occurs http://code.google.com/p/lilypond/issues/detail?id=696 issue 704: whole notes tremolos collide with accidentals http://code.google.com/p/lilypond/issues/detail?id=704 issue 721: Dynamics can collide with notes when applied to cross-staff voices http://code.google.com/p/lilypond/issues/detail?id=721 issue 728: Fingerings collide with accidentals. http://code.google.com/p/lilypond/issues/detail?id=728 issue 757: Slurs should not collide with ledger lines http://code.google.com/p/lilypond/issues/detail?id=757 issue 796: Slurs should not collide with accidentals http://code.google.com/p/lilypond/issues/detail?id=796 issue 930: Collision: differently-sized noteheads in a polyphonic situation http://code.google.com/p/lilypond/issues/detail?id=930 issue 931: Collision: arpeggios collide with other voices http://code.google.com/p/lilypond/issues/detail?id=931 issue 992: Tuplets collide with notes outside the staff http://code.google.com/p/lilypond/issues/detail?id=992 issue 1076: Connected arpeggios collide with previos chord or note http://code.google.com/p/lilypond/issues/detail?id=1076 issue 1091: Dot in \voiceOne collides with stem in \voiceThree in short intervals http://code.google.com/p/lilypond/issues/detail?id=1091 issue 1094: MultiMeasureRest in one voice collides with noteheads in another http://code.google.com/p/lilypond/issues/detail?id=1094 issue 1114: A later note's stem can be to the left of an earlier note's stem http://code.google.com/p/lilypond/issues/detail?id=1114 issue 1175: in crossed voices slurs may collide with dots http://code.google.com/p/lilypond/issues/detail?id=1175 issue 1222: If one fingering has "up" orientation, then that what is "left" collides with accidental http://code.google.com/p/lilypond/issues/detail?id=1222 issue 1230: Dot may collide with flag with some stem's 'length values http://code.google.com/p/lilypond/issues/detail?id=123
Re: Issue 1821 in lilypond: GUB argument list too long
Updates: Labels: -Type-Build -Priority-Critical Type-Critical Comment #5 on issue 1821 by percival.music.ca: GUB argument list too long http://code.google.com/p/lilypond/issues/detail?id=1821 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1827 in lilypond: GUB failure for darwin-x86::cross/gcc target
Status: Accepted Owner: Labels: Type-Critical New issue 1827 by percival.music.ca: GUB failure for darwin-x86::cross/gcc target http://code.google.com/p/lilypond/issues/detail?id=1827 http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg00648.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2
Updates: Labels: -Priority-Medium -Type-Maintainability Type-Enhancement Comment #11 on issue 1780 by percival.music.ca: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1690 in lilypond: old announcements+changes on website
Updates: Labels: -Priority-Medium -Type-Maintainability Type-Other Comment #2 on issue 1690 by percival.music.ca: old announcements+changes on website http://code.google.com/p/lilypond/issues/detail?id=1690 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available
Updates: Cc: -percival.music.ca Labels: -Type-Maintainability Type-Enhancement Comment #3 on issue 1686 by percival.music.ca: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available http://code.google.com/p/lilypond/issues/detail?id=1686 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1638 in lilypond: lilypond-book [quote] hard-codes 5\in
Updates: Status: Duplicate Labels: -Priority-Medium Mergedinto: 1816 Comment #2 on issue 1638 by percival.music.ca: lilypond-book [quote] hard-codes 5\in http://code.google.com/p/lilypond/issues/detail?id=1638 This is probably a duplicate of issue 1816. Let's keep that other issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1816 in lilypond: Lilypond-book music runs off right side of the page
Comment #12 on issue 1816 by percival.music.ca: Lilypond-book music runs off right side of the page http://code.google.com/p/lilypond/issues/detail?id=1816 Issue 1638 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1387 in lilypond: Enhancement: discuss whether non-trivial convert-ly should trace as a comment in .ly files
Updates: Status: Started Owner: percival.music.ca Labels: -Priority-Medium Comment #3 on issue 1387 by percival.music.ca: Enhancement: discuss whether non-trivial convert-ly should trace as a comment in .ly files http://code.google.com/p/lilypond/issues/detail?id=1387 I've recorded this in the GOP questions. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Updates: Labels: -Type-Maintainability Type-Enhancement Comment #25 on issue 1349 by percival.music.ca: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1055 in lilypond: guile 2.0
Updates: Labels: -Type-Maintainability Type-Enhancement Comment #25 on issue 1055 by percival.music.ca: guile 2.0 http://code.google.com/p/lilypond/issues/detail?id=1055 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1000 in lilypond: communicate with upstream texi2html project
Updates: Summary: communicate with upstream texi2html project Labels: -Priority-Low -Frog Comment #7 on issue 1000 by percival.music.ca: communicate with upstream texi2html project http://code.google.com/p/lilypond/issues/detail?id=1000 Since texi2html has been completely rewritten, there is nowhere to "send patches upstream" at the moment. That said, whenever there is a new version of texi2html, it would be good to 1) migrate our docs to that system 2) send (some/most?) of our custom texi2html settings to the upstream project. I'm not expecting any action on this for at least another 2 years. I wouldn't be surprised if it passed 5 years. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 940 in lilypond: unify announcement methods
Updates: Owner: --- Labels: -Priority-Medium Comment #5 on issue 940 by percival.music.ca: unify announcement methods http://code.google.com/p/lilypond/issues/detail?id=940 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 848 in lilypond: clean up news-front.itexi handling
Updates: Summary: clean up news-front.itexi handling Labels: -Priority-Postponed Comment #4 on issue 848 by percival.music.ca: clean up news-front.itexi handling http://code.google.com/p/lilypond/issues/detail?id=848 I'm no longer certain if we want to auto-generate news-front; I kind-of like having the easy control of which news items show up on the main webpage. But it would certainly be nice to handle dates in SI format! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub
Updates: Status: Started Owner: percival.music.ca Labels: -Priority-Medium Comment #9 on issue 980 by percival.music.ca: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 this will be handled in GOP. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth
Updates: Status: Started Owner: carl.d.s...@gmail.com Labels: Patch-new Comment #11 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of tuplet sixteenth http://code.google.com/p/lilypond/issues/detail?id=11 Patch up for review. http://codereview.appspot.com/4941041/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Part_combine_iterator::last_playing_ not initialized
> I'm not top posting.
% valgrind reports that a member of Part_combine_iterator is used
% before being initialized. Initializing last_playing_ = SOLO1 in
% the constructor makes the warning go away.
\version "2.14.2"
\partcombine { s } { s }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
