Re: Bug

On 1 February 2017 at 19.04.40, Trevor Daniels (t.dani...@treda.co.uk) wrote: Simon Albrecht wrote Wednesday, February 01, 2017 5:49 PM  > On 01.02.2017 18:08, Mike Solomon wrote:  >  >> Yeah, just checked it out, you can remove the spurious if (brain fart).  >> I don’t ha

Re: Bug

y comes about by two different people making patches at different times, but the whole passage appears to be from commit a339f8b9865b0f02febd351ba494129d414fb568 Author: Mike Solomon Date: Wed Mar 16 15:07:34 2011 -0400 Fixes Issue 1504, allowing feather beam line breaking. Makes i

Broken horizontal brackets do not avoid treble clef

\version "2.19" % broken horizontal bracket intersects with bottom of treble clef \score { \new Staff \relative c' { f1\startGroup f \break f f\stopGroup } \layout { \context { \Voice \consists "Horizontal_bracket_engraver" \remove "Forbid_line_break_engraver"

Lyrics ending ossia staff push next notes to a new measure

%{ To see the problem, comment the indicated line in and out. %} \version "2.19.15" someMusic = \relative c, { \clef bass a4 a a a << \new Staff \with {alignAboveContext="realBass" } \new Voice = "tempBassVoice" { \clef bass a4 a a a | a a a a R1

Re: cross-staff bug?

On Jul 25, 2014, at 6:19 PM, David Nalesnik wrote: > Hi, > > Attempting to put dynamics above cross-staff notes using the code below leads > to some awful collisions. I've recast my example in three ways, to no avail. > > In the first example, besides the collisions, the final stem is reverse

accidental tuplet number collision

Accidentals should not collide with tuplet numbers. This shows a counter-example. \version “2.19.0" { \override TupletBracket.direction = #UP \times 4/4 { fis''4 fis''! fis''! fis''! } } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://l

Re: nice 2.18 regression tests

On Dec 31, 2013, at 7:52 AM, Keith OHara wrote: > 'lesNereides.ly' collides again. The collision is with a cross-staff slur, > which LilyPond has never so far included in collision-avoidance between > systems. However, we did have 'horizontal-padding' settings so that the > 'm.g.' from the

Re: \parenthesize collision with dots

On Dec 18, 2013, at 1:00 AM, Urs Liska wrote: > If I parentesize a dotted note with > > { \parenthesize f'2. } > > the right paren collides with the dot. > > Urs Do you want the dot to shift to avoid the collision or the parenthesis to encompass the dot? Cheers, MS _

Re: Polyphony--Accidental aligns to stem rather than note

On Nov 26, 2013, at 8:10 AM, ryanmichaelmcclure wrote: > Here is the exact sample of what I am trying to do, except I am writing out > the repeats. I want the eighth notes to have the stems down and the solo > note stem up. > > V

Re: Polyphony--Accidental aligns to stem rather than note

On Nov 26, 2013, at 6:47 AM, ryanmichaelmcclure wrote: > My apologies for my many emails this week--I am off of school for the week > and have time to catch up on my music typesetting. > > I have found that whenever I do two-voice polyphony but flip stems around, > it causes accidentals to alig

Re: lilypond-2.17.28 doesn't build with libc++

On Nov 8, 2013, at 11:15 AM, Thomas Klausner wrote: > Hi! > > I've tried building lilypond-2.17.28 with libc++, the new standard c++ > library for use with llvm (http://libcxx.llvm.org/). > > I have a build failure I don't really know how to fix, it is: > > I know that there are differences be

Re: Multi-measure rests before a new temporary staff is added

On Nov 5, 2013, at 3:01 AM, Steven Weber wrote: > Laziness. The movement I'm typesetting is 600+ measures long with tons of > time changes, and only 15 measures of that are split. That's why LP allows > this kind of construct in the first place, no? Because we still don't have > a good way to

Re: Segfault

On Oct 11, 2013, at 8:18 PM, Colin Campbell wrote: > On 13-10-11 06:55 AM, Mike Solomon wrote: >> \version "2.17.26" >> >> \score { >> \new Staff {} >> \midi {} >> } >> >> Ultra-minimalist composers everywhere are complete

Segfault

\version "2.17.26" \score { \new Staff {} \midi {} } Ultra-minimalist composers everywhere are completely blocked until someone fixes this. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-li

Re: Lilypond 2.17.26 coredumps on tuplet with only skips

On 12 sept. 2013, at 10:54, Thomas Morley wrote: > On my machine the relevant 2.16.-code fails too > > \version "2.16.2" > > \score { >\times 2/3 { s8 s8 s8 } > } > [slightly off subject, as it doesn't t have to do with the bug] I do this sorta thing in many a score. Consider using :

Re: Create different pdf layers

On 1 août 2013, at 11:15, Urs Liska wrote: > I have brought this up before without success. But as my interest reappeared > I'll try it again with a slightly more specific question. > > When LilyPond finally renders its objects 'on paper' how complicated would it > be to allow it to print on l

Re: old-straight-flag + smaller Stem.thickness gives no output and huge overflow

; } >>> >>> When I set Stem.thickness to default (1.3) everything is OK. >>> >>> Version 2.16.2 gives valid output regardless of Stem.thickness value. >> >> Looks like a really scary bug. 2.17.12 seems to have this still work. >> This would have se

Dot and fermata too close for comfort

\relative c''' { a4.^\fermata } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

cyclic dependency for slurred notes with articulations

> I'm not top posting \relative { \tempo "foo" f4->--( e8-.) } Results in a cyclic dependency warning. Remove the tempo and there is no longer the warning. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/b

Making a command line -d option for skipTypesetting

> I'm not top posting It'd be great to have a command line option that specifies the number of measures (or eighth notes or whatever) to typeset at the end of a piece. This way, skipTypesetting can be called from the command line or set as an option in a header file. It'd speed up workflow a lot

Finger-flag collision

> I'm not top posting. \relative c' { \set fingeringOrientations = #'(right) 8 } Results in flag-on-number and number-on-number collisions. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-l

Extra bar-lines appear when cadenzas are mixed with time signatures

It's not the most minimal example in the world, but it's tiny and it shows the problem (check out the "comment me out" line). \version "2.14.0" GRanITzMaLSxcacU= << { fis'32\mp gis' dis'8-. r r16 } { \time 3/8 <<< comment me out to get correct barring \cadenzaOn s16 \cadenzaOff

Re: Issue 1858 in lilypond: unexplained increase in profile reports

On Aug 31, 2011, at 8:50 AM, lilyp...@googlecode.com wrote: > Status: Accepted > Owner: > Labels: Type-Critical Regression > > New issue 1858 by k-ohara5...@oco.net: unexplained increase in profile reports > http://code.google.com/p/lilypond/issues/detail?id=1858 > > The reported 'cells', i

Re: Issue 1828 in lilypond: contextStringTuning creates extra space after first system

On Aug 29, 2011, at 7:07 PM, lilyp...@googlecode.com wrote: > > Comment #7 on issue 1828 by d...@gnu.org: contextStringTuning creates extra > space after first system > http://code.google.com/p/lilypond/issues/detail?id=1828 > > I pushed the simple version only affecting the current context as

Re: Issue 1834 in lilypond: Website: provide link to .ly for examples

On Aug 24, 2011, at 3:19 PM, David Kastrup wrote: > lilyp...@googlecode.com writes: > >> Comment #2 on issue 1834 by colinpkc...@gmail.com: Website: provide >> link to .ly for examples >> http://code.google.com/p/lilypond/issues/detail?id=1834 >> >> Summarising comments on bug-lilypond: >> >> T

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

On Aug 23, 2011, at 6:02 PM, lilyp...@googlecode.com wrote: > > Okay, I revise my comment 13. It looks different. With that backtrace (notice > this=0x12 in Grob::internal_set_property!) it rather looks like the > Engraver_group::acknowledge_grobs has a Grob_info entry in the > announce_infos

Re: Slurs can make dynamics and articulations overlap

t; s1 >> } >> >> >> } >> >> produces the attached output. >> >> I'm not sure whether the two staves are necessary to reproduce it. The >> relevant aspects seem to be: >> >> * accent and dynamics are both below the note (throug

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

On Aug 23, 2011, at 2:38 PM, lilyp...@googlecode.com wrote: > > Comment #13 on issue 1732 by reinhold...@gmail.com: occasional segfault when > compiling input/regression/midi/key-initial.ly > http://code.google.com/p/lilypond/issues/detail?id=1732 > > Looking through the code, it appears as fol

Re: Issue 1235 in lilypond: Accidental overlays stem

On Aug 23, 2011, at 1:26 PM, lilyp...@googlecode.com wrote: > > Comment #9 on issue 1235 by reinhold...@gmail.com: Accidental overlays stem > http://code.google.com/p/lilypond/issues/detail?id=1235 > > +1 to Janek's comment. Shifting the accidental below/above a barline is fine > (the notehead

Re: Issue 1821 in lilypond: GUB argument list too long

On Aug 16, 2011, at 12:58 PM, Reinhold Kainhofer wrote: > Am Tuesday, 16. August 2011, 12:47:13 schrieb Mike Solomon: >> On Aug 16, 2011, at 12:06 PM, David Kastrup wrote: >>> If we can't pass the filenames to a call of lys-to-tely because of >>> command line lengt

Re: Issue 1821 in lilypond: GUB argument list too long

On Aug 16, 2011, at 12:06 PM, David Kastrup wrote: > Reinhold Kainhofer writes: > >> On Di., 16. Aug. 2011 07:46:32 CEST, David Kastrup wrote: >> >>> lilyp...@googlecode.com writes: I think it's literally that we have too many regression test files to fit into the current allowable

Re: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes

On May 4, 2011, at 9:58 AM, Bertrand Bordage wrote: > This isn't a regression. I suggest a medium or high prority. > Here is an example : > > \version "2.15" > << > { a'32[ a' a' a'] } > \\ > { c''[ d'' d'' d''] } > >> > > Regards, > Bertrand The issue would need to be fixed in beam-quant

Re: Footnotes: empty fill-lines in header & footer

On Mar 13, 2011, at 3:17 PM, Nicolas Sceaux wrote: > Le 13 mars 2011 à 19:53, Nicolas Sceaux a écrit : > >> Hi Mike, >> >> First of all, thank you very much for your precious work on footnotes. >> >> The following example demonstrates a strange behavior wrt footnotes: >> >> %% For each empty \