Re: Issue 2216 in lilypond: AU: Document all options for lilypond -dhelp
Ian On 19 March 2012 13:45, Ian Hulin i...@hulin.org.uk wrote: Hi Phil, On 19/03/12 11:31, lilyp...@googlecode.com wrote: Comment #4 on issue 2216 by pkx1...@gmail.com: AU: Document all options for lilypond -dhelp http://code.google.com/p/lilypond/issues/detail?id=2216 I noticed Graham has some commments. I'd also like to make sure that my terminology is correct. I.e. the command -d[symbol]=[value] or --define-default=[symbol]=[value] is this a Scheme 'symbol' or something else? I'd just like it to use the correct terminology. 'symbol' == a command-line option name which is handled at scheme level rather from within the C++ code. Quite often they are boolean flags so they default to using #t or #f (because they are handled using scheme). In other cases, like loglevel, they can use a whole set of string values. Maybe this? -d[option-name]=[value] or --define-default=[option-name]=[value] Thanks, that helps a lot. -- -- James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2216 in lilypond: AU: Document all options for lilypond -dhelp
Updates:
Labels: Patch-new
Comment #8 on issue 2216 by pkx1...@gmail.com: AU: Document all options for
lilypond -dhelp
http://code.google.com/p/lilypond/issues/detail?id=2216#c8
Doc: AU - document -dhelp CLI options
Issue 2216
Add new @node for the -d[Scheme_val] option.
Renamed old node so that it is distinguishable from the
cli using sceheme variables.
Moved all the original -d[symbol] information over and added
some @ref{} for different options.
Other minor syntax changes and spacing edits on surrounding text.
http://codereview.appspot.com/5843060
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2169 in lilypond: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams
Comment #11 on issue 2169 by tdaniels...@gmail.com: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams http://code.google.com/p/lilypond/issues/detail?id=2169 Sorry Colin. There were two: d74afd12749a9d1de0aaac200bb86658091f15c3 f1d318170db686e9215c391a448975d5e88fad91 Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2418 in lilypond: Patch: Don't copy GNUmakefile and *.make from within builddir to builddir
Updates: Labels: Patch-review Comment #9 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and *.make from within builddir to builddir http://code.google.com/p/lilypond/issues/detail?id=2418#c9 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2421 in lilypond: Slur collides with other voice's notehead
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2421 by colingh...@gmail.com: Slur collides with other voice's
notehead
http://code.google.com/p/lilypond/issues/detail?id=2421
Reported by Sebastian Banert:
http://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00832.html
http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/34954
I was able to reproduce the bug. Text of bug report follows:
Hi,
if a note in voiceTwo is above the one in voiceOne, a slur starting in
voiceTwo
will collide with the note head of voiceOne. The following example will
reproduce the problem (and does so with version 2.12.3, I didn't test
2.14.2).
%%%
\version 2.15.34
c''2
\\
{ e''4 (a') }
%%%
Best wishes,
Sebastian Banert
Attachments:
bug.ly 611 bytes
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slur collides with other voice's note head
On Tue, Mar 20, 2012 at 01:13:46AM +, Sebastian Banert wrote:
I'm not top posting.
Hi,
if a note in voiceTwo is above the one in voiceOne, a slur starting in
voiceTwo
will collide with the note head of voiceOne. The following example will
reproduce the problem (and does so with version 2.12.3, I didn't test 2.14.2).
%%%
\version 2.15.34
c''2
\\
{ e''4 (a') }
%%%
Thanks for the bug report, Sebastian. A nice simple example. I was able to
reproduce the bug.
There are a lot of known issues relating to slurs and ties colliding with other
pieces of notation, and the closest I can find is issue 356
http://code.google.com/p/lilypond/issues/detail?id=356
I have created a new tracker 2421 so that we definitely capture your sample. I
suspect it will be merged into one of the other issues by the developers.
http://code.google.com/p/lilypond/issues/detail?id=2421
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2421 in lilypond: Slur collides with other voice's notehead
Comment #1 on issue 2421 by d...@gnu.org: Slur collides with other voice's
notehead
http://code.google.com/p/lilypond/issues/detail?id=2421
This is actually related to solving issue 2411: collision avoidance does
not look at other voices. Here you can see how collision avoidance (and
slur anchoring) work with and without considering other voices:
%%%
\version 2.15.34
f'2
\\
{ e''4 (a') }
\layout { \context { \Staff \consists Slur_engraver } }
%%%
It turns out that neither are fabulous: you want to have the collision
avoidance look at all voices in the staff, but you want to anchor the slur
just off the notes from the starting/ending voice.
Attachments:
ggg.preview.png 2.2 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slur collides with other voice's note head
Colin Hall colingh...@gmail.com writes:
On Tue, Mar 20, 2012 at 01:13:46AM +, Sebastian Banert wrote:
I'm not top posting.
Hi,
if a note in voiceTwo is above the one in voiceOne, a slur starting
in voiceTwo
will collide with the note head of voiceOne. The following example will
reproduce the problem (and does so with version 2.12.3, I didn't
test 2.14.2).
%%%
\version 2.15.34
c''2
\\
{ e''4 (a') }
%%%
Thanks for the bug report, Sebastian. A nice simple example. I was
able to reproduce the bug.
There are a lot of known issues relating to slurs and ties colliding
with other pieces of notation, and the closest I can find is issue 356
http://code.google.com/p/lilypond/issues/detail?id=356
I have created a new tracker 2421 so that we definitely capture your
sample. I suspect it will be merged into one of the other issues by
the developers.
http://code.google.com/p/lilypond/issues/detail?id=2421
Your analysis is excellent, and indeed I would call this another example
of 356.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 356 in lilypond: collision slur/stems+notehead in polyphony
Comment #3 on issue 356 by d...@gnu.org: collision slur/stems+notehead in polyphony http://code.google.com/p/lilypond/issues/detail?id=356 Issue 2421 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2421 in lilypond: Slur collides with other voice's notehead
Updates: Status: Duplicate Mergedinto: 356 Comment #2 on issue 2421 by d...@gnu.org: Slur collides with other voice's notehead http://code.google.com/p/lilypond/issues/detail?id=2421 (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 356 in lilypond: collision slur/stems+notehead in polyphony
Updates: Labels: -Type-Enhancement -Priority-Low Type-Ugly Comment #4 on issue 356 by d...@gnu.org: collision slur/stems+notehead in polyphony http://code.google.com/p/lilypond/issues/detail?id=356 (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 2169 in lilypond: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams
Updates: Status: Verified Comment #12 on issue 2169 by colingh...@gmail.com: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams http://code.google.com/p/lilypond/issues/detail?id=2169 Verifed that those commmits are in the repo and also that they are part of 2.15.34 ___ 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: Patch-new Comment #8 on issue 1690 by julien.r...@gmail.com: old announcements+changes on website http://code.google.com/p/lilypond/issues/detail?id=1690#c8 Tracks old announcements, news and changelogs. Copy announce files for 2.0-2.12 from origin/archive/web into Documentation/misc. Update make/website.make to include old announcements on lilypond.org/misc. Update links to old announcements from lilypond.org/old-news. Add attic section to lilypond.org under community. http://codereview.appspot.com/5843069 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: new lilypond-auto mailing list
On 2012-03-20 00:28, Graham Percival wrote: On Tue, Mar 20, 2012 at 12:11:46AM +0100, David Kastrup wrote: So instead of surprising volunteers by giving them more information than expected we give them less information than expected? Bug squad members shouldn't be reading tracker messages anyway. It's not about bug squad, but about all developers. The comment of the lilypond users to the bug reports are *extremely* important for development. On the other hand, all those hundreds of automated comments to the bug reports are totally unnecessary. To me the main problem is that we have so many automated comments to a bug report that the bug-lilypond list is swamped with those notifications and the relevant human responses are hard to detect (I now typically ignore all bug mails, since it simply takes to long to find out which of the ~50-70 mails per day are automated and which are relevant). 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
Issue 2422 in lilypond: Patch: Archive baselines in LILYPOND_BASELINES directory if specified
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2422 by d...@gnu.org: Patch: Archive baselines in LILYPOND_BASELINES directory if specified http://code.google.com/p/lilypond/issues/detail?id=2422 Archive baselines in LILYPOND_BASELINES directory if specified This has obvious applications for patchy (allowing for a complete directory wipe between patch tests) and a few other things. It also means that if you keep the baseline archives of interesting commits (like the last stable releases) around, you can quickly and easily make check against a preexisting baseline tarball, at least concerning those regtests that existed at that time. http://codereview.appspot.com/5841077 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond 2.15.34 on MacOS X
On Mon, Mar 19, 2012 at 02:50:41PM +, Colin Hall wrote: You may have seen the announcement that version 2.15.34 of Lilypond has been released. It would be great to hear if it works for you on your respective platforms so that I can update the table below. I'll post updates as they come in. Thanks very much to Ole Schmidt, Stan Sanderson, Hans Aikema and Hans Aberg for confirming that Lilypond 2.15.34 launches and successfully typesets various scores on the following platforms: |-+-++-+-+-| | MacOS X | x86/ppc | User | 2.15.32 | 2.15.33 | 2.15.34 | | version | || ok? | ok? | ok? | |-+-++-+-+-| | 10.4.11 | ppc | Ole Schmidt| yes | yes | yes | | | | Valentin Villenave | | | | | | | James Worlton | yes | yes | | |-+-++-+-+-| | 10.4.11 | x86 | Klaus Foehl| no | | | |-+-++-+-+-| | 10.5.8 | ppc | Stan Sanderson | yes | yes | yes | |-+-++-+-+-| | 10.5.8 | x86 | Stan Sanderson | yes | yes | yes | |-+-++-+-+-| | 10.6.8 | x86 | Ole Schmidt| yes | yes | yes | | | | Tim McNamara | | yes | | |-+-++-+-+-| | 10.7.3 | x86 | Eric Schissel | yes | | | | | | Hans Aikema| yes | yes | yes | | | | Brian Alliford | | | | | | | Phillipe | yes | | | | | | Hans Aberg | | | yes | |-+-++-+-+-| Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2418 in lilypond: Patch: Don't copy GNUmakefile and *.make from within builddir to builddir
Comment #10 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and *.make from within builddir to builddir http://code.google.com/p/lilypond/issues/detail?id=2418 Actually, if you want to be in a safe, known place, git reset --hard; git clean -f -x -d will get you there. It will remove things like the test baseline as well, but if you make use of the test baseline archive implemented in issue 2422 (obviously to be located out of the repository checkout), there would not appear to be a significant drawback. Anyway, I'll push this patch to staging soonish. Your objections are about my characterization of this patch as addressing a self-inflicted problem. I am not convinced that it is all that sensible to do in-tree out-of-tree builds, but while the various patchies delight in doing so, there is little point in having more weird things happen as a result than necessary. The current version addresses both the build tree inside of repository as well as the repository inside of build tree arrangements. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2422 in lilypond: Patch: Archive baselines in LILYPOND_BASELINES directory if specified
Updates: Labels: Patch-review Comment #1 on issue 2422 by d...@gnu.org: Patch: Archive baselines in LILYPOND_BASELINES directory if specified http://code.google.com/p/lilypond/issues/detail?id=2422#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2216 in lilypond: AU: Document all options for lilypond -dhelp
Updates: Labels: Patch-needs_work Comment #9 on issue 2216 by d...@gnu.org: AU: Document all options for lilypond -dhelp http://code.google.com/p/lilypond/issues/detail?id=2216#c9 Patchy the autobot says: Patch does not apply to master. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2422 in lilypond: Patch: Archive baselines in LILYPOND_BASELINES directory if specified
Updates: Status: Started Owner: d...@gnu.org Labels: -Patch-review Patch-countdown Comment #2 on issue 2422 by d...@gnu.org: Patch: Archive baselines in LILYPOND_BASELINES directory if specified http://code.google.com/p/lilypond/issues/detail?id=2422 I would like to have this move _fast_ to master since it is supposed to make it considerably less painful for me to run Patchy. It has passed test-patches.py, and I will commit to staging tomorrow barring complaints. When the environment variable LILYPOND_BASELINES is not set (and BASELINE_COMMIT is not set), the behaviour should be identical. This is the most important aspect to review. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2216 in lilypond: AU: Document all options for lilypond -dhelp
Comment #10 on issue 2216 by pkx1...@gmail.com: AU: Document all options for lilypond -dhelp http://code.google.com/p/lilypond/issues/detail?id=2216 David, I have just applied my patch to current master with no issue --snip-- First, rewinding head to replay your work on top of it... Fast-forwarded master to 7a0c49b741de8aa998e17c310d7a4703d7b1712c. james@DellVM:~/lilypond-git$ git am ../Dropbox/LPPatches/0002-Doc-AU-document-dhelp-CLI-options.patch Applying: Doc: AU - document -dhelp CLI options james@DellVM:~/lilypond-git$ --snip-- git-cl always complains if you haven't done a 'pull' before uploading a patch (dirty tree or something). So have I missed something or is the problem on your master? James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2418 in lilypond: Patch: Don't copy GNUmakefile and *.make from within builddir to builddir
Updates: Labels: -Patch-review Fixed_2_15_35 Comment #11 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and *.make from within builddir to builddir http://code.google.com/p/lilypond/issues/detail?id=2418 Pushed as 21315eff86cedc692b2b1ed999eafdf8dbd60ff5 to staging. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2327 in lilypond: Doc for preview command line option is hard to understand
Updates: Status: Verified Comment #13 on issue 2327 by elu...@gmail.com: Doc for preview command line option is hard to understand http://code.google.com/p/lilypond/issues/detail?id=2327 (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 2365 in lilypond: Add 'tabloid' (as valid string) to paper.scm
Updates: Status: Verified Comment #18 on issue 2365 by elu...@gmail.com: Add 'tabloid' (as valid string) to paper.scm http://code.google.com/p/lilypond/issues/detail?id=2365 (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 2367 in lilypond: Notation Reference: Error in footnote documentation
Updates: Status: Verified Comment #8 on issue 2367 by elu...@gmail.com: Notation Reference: Error in footnote documentation http://code.google.com/p/lilypond/issues/detail?id=2367 (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 2216 in lilypond: AU: Document all options for lilypond -dhelp
Comment #11 on issue 2216 by d...@gnu.org: AU: Document all options for lilypond -dhelp http://code.google.com/p/lilypond/issues/detail?id=2216 It is obvious that your patch on Dropbox does not correspond to the latest patch uploaded to the Rietveld issue (I checked using the same master commit you just specified and downloaded the latest patch from Rietveld manually): dak@lola:/usr/local/tmp/lilypond$ git checkout 7a0c49b741de8aa998e17c310d7a4703d7b1712c Note: checking out '7a0c49b741de8aa998e17c310d7a4703d7b1712c'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at 7a0c49b... Doc: CG Typo of Typo dak@lola:/usr/local/tmp/lilypond$ git apply /tmp/issue5843060_2002.diff error: patch failed: Documentation/contributor/administration.itexi:330 error: Documentation/contributor/administration.itexi: patch does not apply ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2370 in lilypond: Obsolete statement in Learning manual
Updates: Status: Verified Comment #8 on issue 2370 by elu...@gmail.com: Obsolete statement in Learning manual http://code.google.com/p/lilypond/issues/detail?id=2370 (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 2376 in lilypond: Automatic footnotes on \null markups causes unexpected results
Updates: Status: Verified Comment #21 on issue 2376 by elu...@gmail.com: Automatic footnotes on \null markups causes unexpected results http://code.google.com/p/lilypond/issues/detail?id=2376 (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 2386 in lilypond: Inconsistent Beam Subdivision
Updates: Status: Verified Comment #13 on issue 2386 by elu...@gmail.com: Inconsistent Beam Subdivision http://code.google.com/p/lilypond/issues/detail?id=2386 (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 2388 in lilypond: Doc: using \voiceXXX for direction and placement
Updates: Status: Verified Comment #12 on issue 2388 by elu...@gmail.com: Doc: using \voiceXXX for direction and placement http://code.google.com/p/lilypond/issues/detail?id=2388 (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 2394 in lilypond: use of Key_signature_engraver in 2.15.33 is incorrect should be key_engraver
Updates: Status: Verified Comment #2 on issue 2394 by elu...@gmail.com: use of Key_signature_engraver in 2.15.33 is incorrect should be key_engraver http://code.google.com/p/lilypond/issues/detail?id=2394 (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 2403 in lilypond: MultiMeasureRest's 'staff-position in RhythmicStaff is wrong per default
Updates: Status: Verified Comment #10 on issue 2403 by elu...@gmail.com: MultiMeasureRest's 'staff-position in RhythmicStaff is wrong per default http://code.google.com/p/lilypond/issues/detail?id=2403 (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: Patch-review Comment #9 on issue 1690 by d...@gnu.org: old announcements+changes on website http://code.google.com/p/lilypond/issues/detail?id=1690#c9 Patchy the autobot says: LGTM. ___ 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
Comment #10 on issue 1690 by d...@gnu.org: old announcements+changes on website http://code.google.com/p/lilypond/issues/detail?id=1690 Patchy forgot to mention: Trying 1690 with /usr/local/tmp/lilypond/issue5843069_1.diff /usr/local/tmp/lilypond/issue5843069_1.diff:964: space before tab in indent. c8 d8 \quote 2 oboe es8 gis /usr/local/tmp/lilypond/issue5843069_1.diff:1123: space before tab in indent. 'NoteHead heads, or tails? /usr/local/tmp/lilypond/issue5843069_1.diff:1124: space before tab in indent. '(0 . -3)) warning: 3 lines add whitespace errors. /usr/local/tmp/lilypond/issue5843069_1.diff:1855: new blank line at EOF. + warning: 1 line adds whitespace errors. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2390 in lilypond: Notation Reference: General tidy up - @seealso @knownissue spacing
Updates: Status: Verified Comment #7 on issue 2390 by elu...@gmail.com: Notation Reference: General tidy up - @seealso @knownissue spacing http://code.google.com/p/lilypond/issues/detail?id=2390 at a short glance it looks uniform! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2382 in lilypond: Website: colors in Community menu are wrong
Updates: Status: Verified Comment #6 on issue 2382 by elu...@gmail.com: Website: colors in Community menu are wrong http://code.google.com/p/lilypond/issues/detail?id=2382 (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 2423 in lilypond: lilypond-book fails to include a file from a parent directory
Updates: Status: Started Comment #1 on issue 2423 by julien.r...@gmail.com: lilypond-book fails to include a file from a parent directory http://code.google.com/p/lilypond/issues/detail?id=2423 git bisect points to a3036a217ddf3ac281c534caf7d76a151d67d805 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2423 in lilypond: lilypond-book fails to include a file from a parent directory
Comment #2 on issue 2423 by julien.r...@gmail.com: lilypond-book fails to include a file from a parent directory http://code.google.com/p/lilypond/issues/detail?id=2423 http://codereview.appspot.com/5846075 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2423 in lilypond: lilypond-book fails to include a file from a parent directory
Updates: Labels: -Type-Scripts Type-Critical Patch-new Comment #3 on issue 2423 by gra...@percival-music.ca: lilypond-book fails to include a file from a parent directory http://code.google.com/p/lilypond/issues/detail?id=2423 (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 1964 in lilypond: lilydev 2.5
Comment #33 on issue 1964 by pkx1...@gmail.com: lilydev 2.5 http://code.google.com/p/lilypond/issues/detail?id=1964 ok I think I have all this done now. I am going to give it a test run for a few days on my own system (eat my own dog food so to speak). If it does work (it's based on the 10.04) where can I upload it too? It's around 900mb as an iso. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2272 in lilypond: Long monosyllabic words collide with barlines
Updates: Labels: Patch-new Comment #9 on issue 2272 by mts...@gmail.com: Long monosyllabic words collide with barlines http://code.google.com/p/lilypond/issues/detail?id=2272#c9 Axis group interface ignores column rank for pure-from-neighbor-interface http://codereview.appspot.com/5843063 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Combining lyrics lines
Le 19/03/2012 12:13, Eluze disait : I think this needs some adaptation: - the lyrics mum and dad don't fit to the voices - should they be inversed!? Oops! I'm so used to the inverted situation with my parents! - Reedmace Star had proposed to use \voiceOne and \voiceTwo (which is quite usual when notating 2 voices in 1 staff): this helps the singers to locate their part (and also eliminates the warnings about clashing notes). But with the stems going down the lyrics are moved downwards, too, and they don't seem to be on one line anymore. (maybe adding some kind of padding could help). Depending on the ambitus, \voiceXXX is not optimal, and there should be few warnings about clashing note columns. By the way, what I've used with King Arthur is a third voice with lyrics aligned above for the overlapping (see page 106 of the full score available on CPDL, bar 122). I also think there are some LilyPond features that will not work in the normal way and should be discussed: - stanza numbers Having tried it, it appears that the one who doesn't sing on the first beat in the line is not mentioned (bug?). - vocalName (shortVocalName) Of no use in such a case: when a soloist shares the staff with the choir part, there is usually just a markup when switching (solo/tutti), or you change the instrument/vocal name which is attached to the *staff*. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2423 in lilypond: lilypond-book fails to include a file from a parent directory
Updates: Labels: Patch-review Comment #4 on issue 2423 by julien.r...@gmail.com: lilypond-book fails to include a file from a parent directory http://code.google.com/p/lilypond/issues/detail?id=2423#c4 Patchy the autobot says: LGTM. ___ 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
Comment #11 on issue 1690 by julien.r...@gmail.com: old announcements+changes on website http://code.google.com/p/lilypond/issues/detail?id=1690#c11 Patchy the autobot says: LGTM. Whitespace corrected. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2385 in lilypond: Translated donwnload page does not show correct information for MacOSX
Comment #3 on issue 2385 by harmathdenes: Translated donwnload page does not show correct information for MacOSX http://code.google.com/p/lilypond/issues/detail?id=2385 Done in Hungarian (commit 3f1432a63bf849f003b67e8b481f4e38405f6253). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2272 in lilypond: Long monosyllabic words collide with barlines
Updates: Labels: Patch-review Comment #10 on issue 2272 by d...@gnu.org: Long monosyllabic words collide with barlines http://code.google.com/p/lilypond/issues/detail?id=2272#c10 Patchy the autobot says: LGTM. Interesting spacing changes in accidental-broken-tie-spacing and accidental-tie: in both cases, accidentals move somewhat closer after a line break. Not enough of a difference to look significantly better or worse, but I thought I'd mention it. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2371 in lilypond: Patch: Fix crash when unknown grob name is passed to ly:engraver-make-grob
Updates: Labels: -Patch-countdown Patch-needs_work Comment #7 on issue 2371 by colinpkc...@gmail.com: Patch: Fix crash when unknown grob name is passed to ly:engraver-make-grob http://code.google.com/p/lilypond/issues/detail?id=2371 David's comment on Rietveld, for reference: dak 3 hours, 29 minutes ago #7 http://codereview.appspot.com/5715053/diff/2001/lily/engraver-scheme.cc File lily/engraver-scheme.cc (right): http://codereview.appspot.com/5715053/diff/2001/lily/engraver-scheme.cc#newco... lily/engraver-scheme.cc:42: programming_error (cannot create grob); This gives no helpful indication of where the error occured, and triggers problems later in unrelated code. That's not better than a segfault: neither is better than something that shouldn't happened somewhere. You could check whether cause is a grob in which case you can call unsmob_grob (cause)-programming_error on it in order to give the error message a _source_ indicator, or a stream-event in which case unsmob_event (cause)-origin ()-programming_error would deliver a suitable source indicator for the error. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2400 in lilypond: Dots no longer aligned between voices
Updates: Labels: -Patch-countdown Patch-push Comment #12 on issue 2400 by colinpkc...@gmail.com: Dots no longer aligned between voices http://code.google.com/p/lilypond/issues/detail?id=2400 Counted down to 20120320, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2389 in lilypond: Patch: Fix make error in regression tests coming from midi2ly
Updates: Labels: -Patch-countdown Patch-push Comment #11 on issue 2389 by colinpkc...@gmail.com: Patch: Fix make error in regression tests coming from midi2ly http://code.google.com/p/lilypond/issues/detail?id=2389 Counted down to 20120320, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2406 in lilypond: Patch: Fix mordents and pralltriller in articulate.ly
Updates: Labels: -Patch-countdown Patch-push Comment #8 on issue 2406 by colinpkc...@gmail.com: Patch: Fix mordents and pralltriller in articulate.ly http://code.google.com/p/lilypond/issues/detail?id=2406 Counted down to 20120320, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2272 in lilypond: Long monosyllabic words collide with barlines
Comment #12 on issue 2272 by k-ohara5...@oco.net: Long monosyllabic words collide with barlines http://code.google.com/p/lilypond/issues/detail?id=2272 Interesting spacing changes in accidental-broken-tie-spacing This was worth mentioning, because in fact the current patch defeats the code that this patch was meant to test. The spacing should not change if we remove the tie, but with the patch it does change. It looks very easy to fix the patch. An intervening bug-fix, issue 1785, made the failure mode of this test less obvious than it was when the test was written. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
