Re: Ski Emoji Error

On Tue, Apr 24, 2018 at 6:10 AM, James Lowe wrote: > > > Probably depends on the Ghostscript version? Looks fine here: > > Well it looks OK but I get the same 'error' with gs version 9.22 so I > compiled and installed 9.23 and I no longer get this 'failed files' message. >

Ski Emoji Error

Minimal Example: = \version "2.19.80" \markup "⛷" = The end of the output from lilypond -V ski.ly: = Converting to `ski.pdf'... Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite

Re: Mark / Barcheck Bug (#1626) Appearing Again

be trying to do \mark \default or \mark "C" instead. -Jay Anderson ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Hairpins not aligned/symmetrical

On Mon, Jul 21, 2014 at 1:39 PM, Janek Warchoł janek.lilyp...@gmail.com wrote: 2014-07-21 22:15 GMT+02:00 Steven Weber pant...@hotmail.com: Try: \relative c' { f8.\ d16 g4.\ f8\! } Nevertheless, what Aliosha says is a valid feature request (it's not always desirable to have decrescendo

Re: 2.19.x Point and click references

On Sun, Apr 27, 2014 at 11:04 PM, David Kastrup d...@gnu.org wrote: When compiling the above files the point-and-click links do not point to the '00.ily' file. Instead they all point to the final line of 'point_and_click_2.19.ly'. In 2.18 this worked correctly. Without actually testing it, I

2.19.x Point and click references

point_and_click_2.19.ly: = \version 2.19.5 makeScore = #(define-void-function (parser location) () (let ((score #{ \score { \new Staff { \include 00.ily } } #})) (add-score parser score)))

Slur padding on dotted notes

This is a nitpick, but it's noticeable. \version 2.19.2 % and 2.18.0 \score { \new Staff \relative c''' { %non-dotted \time 4/4 g4( f) g( a) | g4~ g a~ a | %dotted \time 12/8 g4.( f) g( a) | %Slurs pushed further away than necessary. g4.~ g a~ a | %Ties look ok

Midi early start (2.19.2)

Removing the Dynamic_performer causes rests at the start of a piece to be skipped causing misalignment with other voices. I've only tested this with 2.19.2 and 2.18.0. It works correctly in 2.18.0. \version 2.19.2 % Work in 2.18.0 \score { \new Staff \relative c' { R1*3 e1 e e | }

Re: \epsfile relative file locations

On Fri, Nov 29, 2013 at 5:43 PM, Eluze elu...@gmail.com wrote: thanks for this workaround - it works as expected. As long as your command line is 'lilypond file.ly' and the eps file is imported from file.ly. What's the correct way to get the name of the current file? I looked for a little while,

\epsfile relative file locations

With the normal \include command and #(ly:set-option 'relative-includes #t) relative includes work. However \epsfile doesn't follow relative includes. For instance if you have a.ly which uses b.eps and compile it from a different directory (e.g. 'lilypond ../a.ly') it will fail. Here's a

Re: show-available-fonts output can't be piped

stderr. $ lilypond -dshow-available-fonts 2 fonts.txt $ lilypond -dshow-available-fonts 21 | less -Jay On Wed, Jul 10, 2013 at 10:26 PM, Mark Polesky markpole...@yahoo.com wrote: Am I overlooking something simple? These don't do what I'd expect: $ lilypond -dshow-available-fonts | less

Re: 2.17.16 vs 2.17.17 Page Breaking

On Sat, May 4, 2013 at 7:21 PM, Keith OHara k-ohara5...@oco.net wrote: I cannot reproduce the full problem. Has anyone seen LilyPond print 'annotate-spacing' output where both the limits for the top staff are negative numbers? I figured out where this was coming from. I was using something

Re: 2.17.16 vs 2.17.17 Page Breaking

On Wed, May 1, 2013 at 12:15 AM, Keith OHara k-ohara5...@oco.net wrote: Nothing was intended to change page-breaking between those versions. However, almost anything changing layout will change the page-breaking when pages are close to full. If one of these things puts the page-breaking back

Table of contents with multiple files

File 'toc_a.ly' == \version 2.17.14 \markuplist \table-of-contents \pageBreak \tocItem A \markup A \pageBreak \tocItem B \markup B \pageBreak == File 'toc_b.ly' == \version 2.17.14 \markuplist \table-of-contents \pageBreak \tocItem C \markup C

Odd spacing with dynamics

\version 2.17.14 \paper { tagline = ##f } filler = \repeat unfold 6 {c4 c c c | \noBreak} \score { \new Staff \relative c' { c4 c c c | \noBreak c c2 c8 c | \filler } } \score { \new Staff \relative c' { c4 c c c | \noBreak {c c2 c8 c |} {s2\ s\

Re: Add tempo spanners

On Tue, Feb 12, 2013 at 5:43 PM, Colin Hall colingh...@gmail.com wrote: It would be great to have a TempoTextSpanner, for example in order to handle common notation such as rit. - - - - a tempo or rall - - - - I do not see this request tracked yet. Thanks for the report, Xavier, but

Re: 2.16.0 and 2.16.1 change with #{ #} syntax

On Tue, Jan 15, 2013 at 2:14 AM, David Kastrup d...@gnu.org wrote: It is somewhat embarrassing, but in my local stable branch I had already collected a few of the file/parser/EOF-related fixes in 2.17 when I told Philip to go ahead with releasing 2.16.2. I suppose I should complete the

2.16.0 and 2.16.1 change with #{ #} syntax

In 2.16.0 creating a book inside #{ #} returned the book. In 2.16.1 and 2.16.2 this is no longer always the case. Here's an example which fails: \version 2.16.2 makeBook = #(define-void-function (parser location) () (let ((the-book #{ \book { \include

Cue Stem Alignment of Merged Noteheads

\version 2.16.0 mus = \relative c' { c8 d e f g a b c } \score { \new Staff \new CueVoice { \voiceOne % Workaround: %\override Stem #'X-offset = #1.22 \mus } \new Voice { \voiceTwo \mus } } The cue stems look like they're

Dash span bars broken with alignAboveContext

\version 2.15.41 mus = \repeat unfold 5 c'1 \score { \new StaffGroup \with { \override SpanBar #'glyph-name = #dashed } \new Staff=x { \mus \mus \new Staff \with { alignAboveContext = x } \mus } } This example works in 2.14.2 with dash

Tuplet numbers placed incorrectly

\version 2.15.33 \paper { ragged-right = ##t } \score { \new Staff \relative c' { R1 | \break \times 2/3 {e8(- a e)} } } In this example the tuplet number is placed within the staff. Taking out the break, the accent, or the slur causes the tuplet to be placed correctly. I haven't

Re: Abrupt end of interpreting music (segmentation fault)

On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes m...@philholmes.net wrote: I don't normally install LilyPond on my Linux box - I simply run a self-compiled version.  It's 64-bit Ubuntu and on this, your file compiles and runs fine.  So I'm assuming (if you know better, please say) that this is

Endless Loop

Compiling this score (reduced from a larger score) never terminates: = \version 2.15.30 \score { \new Staff \relative c' { R1 | \stopStaff R1 | r2 } } = If I'm stopping the staff I should probably be using spacer rests instead and this problem

Beam Collides with Clef Number

\version 2.15.28 \score { \new Staff \relative c'' { \clef treble c8^[ \clef bass^8 e,] } } I'm pretty sure this is an OctavateEight created with the clef. Is there a way to tell the beam to avoid it without code changes? -Jay attachment:

Tuplet Bracket Spacing Bug

\version 2.15.26 \score { \new Staff \relative c'' { \times 2/3 {c4\ff c c} } } It looks like the bracket is making space for the dynamic, but the dynamic is staying outside anyway. The same effect happens with beamed tuplets, but in that case there's no bracket to move. It was

Segfault 2.15.23 Span_bar_stub_engraver

I've been unable to create a good small example so far. When I take out seemingly unrelated sections it compiles which makes it difficult to narrow down. Removing the Span_bar_stub_engraver from my PianoStaff fixes the segfault, but what won't work if I do this? Below is at least the stack trace

Paper block ordering

In 2.15.19 the ordering of things in the paper block matters where it didn't before. An example which removes the first system indent: \version 2.15.19 \paper { indent = 0\in #(set-paper-size letter) %indent = 0\in %Move the indent here to have the indent take effect. }

Add 6x9 Paper Size

6 x 9 in. isn't currently available. I haven't found a standard name for this size. Lulu calls it 'US Trade', http://en.wikipedia.org/wiki/Book_size calls it 'octavo'. In any case it seems to be a fairly common size that would be useful to add (and custom sizes are clunky to add and maintain - is

Re: Add 6x9 Paper Size

On Fri, Sep 30, 2011 at 10:47 AM, m...@apollinemike.com m...@apollinemike.com wrote: On Sep 30, 2011, at 7:43 PM, Peekay Ex wrote: http://code.google.com/p/lilypond/issues/detail?id=1949 Thanks #(set! paper-alist (cons '(6x9 cons (* 6 in) (* 9 in)) paper-alist)) #(set-default-paper-size 6x9)

Lyrics alignment to notes

\version 2.14.2 words = \lyricmode { %Uncomment this to delay alignment of new lyrics by one note. %\set stanza = 1. { a b c d } \new Lyrics \lyricsto melody { a b c d } } melody = \relative c' { c c c c } \score { \new Staff \new Voice=melody \melody \new

AmbitusAccidental avoid-slur not set?

\version 2.14.1 \score { \new Score { \new Voice \with {\consists Ambitus_engraver} { cis4( ees) } } } This results in this warning: warning: Ignoring grob for slur: AmbitusAccidental. avoid-slur not set? This may be more of a feature request. I believe this

Re: Clef change placed outside score

On Wed, Jun 15, 2011 at 6:11 AM, Ralph Palmer ralphbugl...@gmail.com wrote: This has  been submitted as Issue 1695 : http://code.google.com/p/lilypond/issues/detail?id=1695 Thanks. I think I found a couple workarounds: musy = \relative c' { \clef treble \override

Clef change placed outside score

\version 2.14.1 %The bass clef in the lower staff is placed to the left of the staff. If either %the tempo mark is removed or the triplets are changed to a quarter note the %the clef is placed correctly. This was not an error in 2.12.3. musx = \relative c' { % Change this to c4 for correct

Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice

On Fri, Apr 15, 2011 at 7:59 AM, lilyp...@googlecode.com wrote: Comment #3 on issue 1613 by bordage@gmail.com: Beamed stems too long when avoiding low note in other voice http://code.google.com/p/lilypond/issues/detail?id=1613 Han-Wen's commit has broken Beam_collision_engraver. One

merge-rests.ily w/ text on full measure rest segfault 2.13.53 (and from git)

This uses merge-rests.ily which is included with issue 1228 (http://code.google.com/p/lilypond/issues/detail?id=1228). I'm running ubuntu x86-64 linux (2.6.35-22-generic). Below is a minimal example. Two things make the segfault go away: remove the mergeRests from the layout block and removing the

Slur+Dot Collision

This is not a regression from 2.12. I know how to manually fix it, but it'd be nice if it avoided the dot automatically. Related bugs: 868, 1091, 1174, 1230, 1352. I didn't see any listed related to dot-slur collisions specifically so I thought it may be useful. Thanks! -Jay \version

Unicode PDF titles garbled

An example: \version 2.13.48 \header { title = Non Lo Farò Più composer = Johann Baptist Strauß } \score { \new Staff c'1 } When viewing the pdf the title shows as Non Lo Farò Più. I've only tested this with Evince and Okular. In searching about the problem people suggest that the text

Re: Segfault 2.13.47

On Tue, Feb 1, 2011 at 1:46 PM, Keith OHara k-ohara5...@oco.net wrote: ... on both WinXP and Linux and could not find a segfault. It happens consistently for me (linux 2.6.35, x86_64). Since it's such a difficult to reproduce, narrow case it's probably best not to worry about. Filling in the

Re: Segfault 2.13.47

On Sat, Jan 29, 2011 at 11:02 PM, Paul Scott waterho...@ultrasw.com wrote: This says 2.13.48. Right. In order to get debug symbols I built it out of git which is 2.13.48, but I originally saw the error with 2.13.47. -Jay (fellow arizonian) ___

Re: Segfault 2.13.47

On Sun, Jan 30, 2011 at 11:27 AM, Keith OHara k-ohara5...@oco.net wrote: I wish you luck in making a small example. Maybe you can test an earlier Lilypond version on your complete score? Do you use Reinhold's new (not yet documented) \partcombineTogether, etc., that appeared in 2.13.35 ?

Segfault 2.13.47

Below is the gdb trace from the segfault: GNU gdb (GDB) 7.2-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent

Re: New language feature breaks lilypond-words

On Sun, Dec 19, 2010 at 12:27 AM, Patrick McCarty pnor...@gmail.com wrote: Not sure how to implement a proper fix at the moment, so I've opened a tracker issue: https://code.google.com/p/lilypond/issues/detail?id=1457 Thanks for looking into this. In my local lilypond install I've disabled

Re: New language feature breaks lilypond-words

On Sat, Dec 11, 2010 at 5:09 PM, Patrick McCarty pnor...@gmail.com wrote: Thanks for the report, Jay.  The note-name definitions have just moved from the ly/ directory to the scm/ directory, so I've adapted your patch to use the new location. Thanks for taking care of this. Much faster than I

New language feature breaks lilypond-words

This is a small annoyance, but one I didn't see reported. lilypond-words.py used the language files to generate the list of lilypond words. Since these language files now only include \language mylanguage many note names are not being found. The result is vim syntax highlighting (and I imagine

Re: DynamicTextSpanner is not fully contained in parent spanner

On Sun, Sep 12, 2010 at 12:55 PM, Neil Puttock n.putt...@gmail.com wrote: You can still use the old method for hiding lines: \override DynamicTextSpanner #'dash-period = #-1 Yeah, it looks like this is the preferred method since it doesn't have this line break problem.

Re: Tempo Segmentation Fault

On Fri, Sep 10, 2010 at 1:07 AM, Phil Holmes m...@philholmes.net wrote: Related to this? http://code.google.com/p/lilypond/issues/detail?id=1251 Yep, that's it. I guess I missed it in my searching. Thanks. -Jay ___ bug-lilypond mailing list

Re: DynamicTextSpanner is not fully contained in parent spanner

On Fri, Sep 10, 2010 at 12:52 AM, Urs Liska lilyli...@googlemail.com wrote: Am 10.09.2010 06:33, schrieb Jay Anderson: \version 2.13.32 \score {   \new Staff \relative c'   {     %Works fine over break:     c1\cresc     \break     c1\f     \override DynamicTextSpanner #'style

Tremolo + Chord Repetition Error

\version 2.13.32 \new Staff \relative c' { %Causes error: c e8 q q q \repeat tremolo 4 q | %This works: %c e8 q q q \repeat tremolo 4 c e | } Error: Interpreting music... /home/jay/lilypond/usr/share/lilypond/current/scm/lily-library.scm:210:5: In procedure ly:book-process in expression

DynamicTextSpanner is not fully contained in parent spanner

\version 2.13.32 \score { \new Staff \relative c' { %Works fine over break: c1\cresc \break c1\f \override DynamicTextSpanner #'style = #'none c1\cresc \break c1\f } } dts.ly:13:6: programming error: Spanner `DynamicTextSpanner' is not fully contained in

Tempo Segmentation Fault

\version 2.13.32 \score { \new Staff { \tempo Andante 4=63 R1 } \new Staff { R1 } \layout { } } $ lilypond seg.ly GNU LilyPond 2.13.32 Processing `seg.ly' Parsing... Interpreting music... Preprocessing graphical objects...Segmentation fault

Re: Text cresc *without dashed line* and Y-offset

On Sun, May 30, 2010 at 2:03 PM, Neil Puttock n.putt...@gmail.com wrote: On 28 May 2010 17:48, Xavier Scheuer x.sche...@gmail.com wrote: Shouldn't we open an issue about this on the tracker, at least to keep track on this discussion and your very interesting proposal? I should have a patch

cueDuring + tuplet warning

\version 2.13.22 one = \relative c' { c4 c c \times 2/3 {c8 c c} | c8 c c c c c c c | } \addQuote ONE \one two = \relative c' { R1 | \cueDuring #ONE #UP {R1 |} } \score { \new Staff \two } == Results in this warning: cue_prob.ly:5:9: warning: No tuplet to end c4 c c

Re: RhythmicStaff Multimeasure Rests

On Tue, Mar 9, 2010 at 3:19 PM, Neil Puttock n.putt...@gmail.com wrote: \override RhythmicStaff.MultiMeasureRest #'staff-position = #0.01 Thanks. That works great. Now I just have to deal with \context{\RemoveEmptyRhythmicStaffContext} killing my settings. I remember following the discussion

Re: RhythmicStaff Multimeasure Rests

On Fri, Mar 5, 2010 at 10:31 PM, Jay Anderson horndud...@gmail.com wrote: \version 2.13.15 \new RhythmicStaff {  %\override Staff.MultiMeasureRest #'extra-offset = #'(0 . -1)  R1 } Of course this doesn't quite work because all multi measure rests are moved and not just single whole measure

Tuplet bracket over tremolo

\version 2.13.15 \new Staff { %\override TupletBracket #'transparent = ##t \times 2/3 {\repeat tremolo 3 c'8} } In previous versions the above worked as expected: a '3' over a dotted quarter with a eighth tremolo beam. (I've use this in 2.12 without problems.) With the latest 2.13.15 release

RhythmicStaff Multimeasure Rests

\version 2.13.15 \new RhythmicStaff { %\override Staff.MultiMeasureRest #'extra-offset = #'(0 . -1) R1 } The rest should be below the staff line instead of floating above the staff line. It looks like it's placed where it would be on a 5 line staff (below 2nd line from the top). Uncomment the

Re: Issue 641 in lilypond: error: script direction not yet known when using implicit Voice contexts

On Thu, Feb 18, 2010 at 9:50 PM, lilyp...@googlecode.com wrote: % This example has the same fix/workaround as issue 641. % There is no warning in this case. Instead the hairpins % end at the end of the markup instead of at the correct % location. I spoke too soon. I can't figure out how to

Re: auto-beam in pickup-bars with grace note

grisu_76 christian.hummer at univie.ac.at writes: Some ideas? regards, Christian See issue 372: http://code.google.com/p/lilypond/issues/detail?id=372 -Jay ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Programming error: script direction not yet known

\new Voice is a better option to avoid adding a key signature when transposing. Enhancement is fine. Thanks! -Jay On Wed, Jun 18, 2008 at 12:39 AM, Valentin Villenave [EMAIL PROTECTED] wrote: 2008/6/18 Jay Anderson [EMAIL PROTECTED]: Adding a key signature fixes the errors

Programming error: script direction not yet known

\version 2.11.49 \new Staff \relative c'' { %\key c \major %Add a key to correct programming errors. { c16 e a g f e d c } { s16( s) s-. s-. s( s) s-. s-. } } I didn't find this one in the bug tracker. I'm swapping out the rhythm on the same passage and this error is created for

Text from decrescendo spanner not kept inside line

Below the sempre dim. isn't kept inside the line. Shouldn't this be taken into account? The workaround of course is to put a manual \noBreak in. -Jay \version 2.11.49 \score { \new Staff \relative c' { \override Score.PaperColumn #'keep-inside-line = ##t \override

Re: Minor vim syntax improvements

in re.findall (r(?m)^\s*([a-zA-Z]+)\s*=, s)] +keywords += [w for w in re.findall (r(?m)^\s*\?([a-zA-Z]+)\? \s*=, s)] Cheers, - Graham On Sat, 17 May 2008 16:36:53 -0700 Jay Anderson [EMAIL PROTECTED] wrote: Attached is a patch which should make forte dynamic highlighted. It also fixes this: 'c

Minor vim syntax improvements

17 00:00:00 2001 From: Jay Anderson [EMAIL PROTECTED] Date: Sat, 17 May 2008 16:16:37 -0700 Subject: [PATCH] Minor fixes for vim syntax highlighting. --- buildscripts/lilypond-words.py |2 +- vim/lilypond-syntax.vim|6 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff

Another arpeggio collision

When using cross staff arpeggios a collision can occur if accidentals cause the arpeggio to be moved to the left too much. (Possible related issue: 556) Thanks! -Jay \version 2.11.42 \paper { ragged-right = ##t } \book { \new PianoStaff \set PianoStaff.connectArpeggios = ##t

vim no formatting for \f

I would expect \f to look similar to other dynamic markings like \p or \mf when using vim. Adding it to the .../usr/share/lilypond/current/vim/syntax/lilypond-words.vim will fix this. Thanks! -Jay ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Another arpeggio collision

Great! Thanks that worked wonderfully. Thanks! On Fri, Mar 28, 2008 at 2:41 PM, Neil Puttock [EMAIL PROTECTED] wrote: Hi Jay, I've noticed this happening recently. As a workaround I've been setting #'infinite-spacing-height = ##t whenever it occurs. Here's a related example with one

Re: repeatTie does not work in chords

Papa Eric papa.eric at free.fr writes: This adds a repeat tie on both notes, not only b: Try: \new Voice {b\repeatTie} g' It's ugly and you'll get a warning, but I think it will do what you want. -Jay ___ bug-lilypond mailing list

Unwanted tie direction

This seems very similar to issues 440 and 434, but here there is no forced line break. I can't really tell if it is the same exact issue or not. -Jay \version 2.11.42 \paper { ragged-right = ##t } \score { \new Staff \relative c'' { b1~ | b~ | b2 r | } }

Re: keep-inside-line doesn't adjust for long marks

[EMAIL PROTECTED] wrote: On 10/3/07, Jay Anderson [EMAIL PROTECTED] wrote: This would be nice to have, but it's not a huge problem. At the very least perhaps a comment should be added to section 5.7 Avoiding tweaks with slower processing which states that keep-inside-line doesn't affect

keep-inside-line doesn't adjust for long marks

This would be nice to have, but it's not a huge problem. At the very least perhaps a comment should be added to section 5.7 Avoiding tweaks with slower processing which states that keep-inside-line doesn't affect marks. Thanks for the great work! -Jay Anderson \version 2.11.34 \score

Re: \appoggiatura disables autoBeam

Mats Bengtsson mats.bengtsson at ee.kth.se writes: I'm really surprised that this issue hasn't popped up earlier. I remember running into this a couple of months back (http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/10045). I believe the plan was to add it to issue 34

Staff.voltaOnThisStaff = ##t is default

I'm not totally sure this is a bug or a decision, but it conflicts with what is stated in the manual in section 6.7.2 Repeat syntax: Brackets for the repeat are normally only printed over the topmost staff. I think I prefer it set to false. Also see:

Re: cross staff/voice arpeggio error

get the error of course. Is there another option which would allow for both? Thanks again for looking at this. -Jay Anderson \version 2.11.21 \layout { ragged-right = ##t } \new PianoStaff \set PianoStaff.connectArpeggios = ##t \new Staff \with {\consists Span_arpeggio_engraver} \relative c

cross staff/voice arpeggio error

\relative c'' { c2 c2\arpeggio } \new Staff \relative c'' { { c2\arpeggio c2\arpeggio } \\ { g4\arpeggio a g4\arpeggio a } } -Jay Anderson ___ bug-lilypond mailing list bug-lilypond@gnu.org http

Re: segfault 2.11.20

I haven't been able to get a good reduced example. A full piece which has a segfault on my linux box and the malloc error on my wife's mac can be looked at with subversion: 'svn co https://open-scores.svn.sourceforge.net/svnroot/open-scores/DukasVillanelle/trunk DukasVillanelle' Try to compile

Re: segfault 2.11.20

Jay Anderson wrote: I can't narrow this one down too much, it's really weird. For example when I remove the two commented out lines the segfault goes away. -Jay (I'm on Fedora Core 6) = \version 2.11.20 \score { \new PianoStaff \new Staff=RH \relative c' { c4 d e

segfault 2.11.20

I can't narrow this one down too much, it's really weird. For example when I remove the two commented out lines the segfault goes away. -Jay (I'm on Fedora Core 6) = \version 2.11.20 \score { \new PianoStaff \new Staff=RH \relative c' { c4 d e f | } \new Dynamics

bug 279

When compiling the example provided with bug 279 (http://code.google.com/p/lilypond/issues/detail?id=279) I get the following error: GNU LilyPond 2.11.19 Processing `test.ly' Parsing... Interpreting music... [8][16][24][32][40][48][56][64][72][80][88][96][104][112][117] Preprocessing graphical

Re: Text Spanners broken in 2.11.17

\override Glissando #'bound-details #'right #'text = \markup { \hcenter \bold down } ... which works for text spanners, too. Two overrides now instead of one (if you're wanting to override edge text at both the left and right of the spanner). But the upside is that padding and positioning of

grace + partial autobeaming problem

It seems when a piece starts with a grace in a partial measure the autobeaming for the rest of the piece gets messed up. A work around is to add a spacer rest to the start. \version 2.11.18 \paper { ragged-right = ##t } \score { \new Staff \relative c' { \partial 8 \grace c16 c c c c

Text Spanners broken in 2.11.17

The examples in section 8.1.3 Text spanners in the 2.11.17 manual are broken. The text is missing from the spanners. Is there a new way to do this or is this a regression? I haven't seen this mentioned yet on this list or in the bug database. Thanks! -Jay

Bad tuplet beam

I managed to simplify my test file to get a segfault with the following: = \version 2.11.16 \paper { ragged-right = ##t } %57 - no segfault %58 - segfault spacer = { \repeat unfold 58 R2 } \score { \new PianoStaff \new Staff = RH { \time 2/4 \clef treble \spacer

Re: 2.11.15 debug help / detached beam

Ghostscript SVN PRE-RELEASE 8.56: Can't find initialization file gs_init.ps. GS exited with status: 256 On 2/2/07, Graham Percival [EMAIL PROTECTED] wrote: Jay Anderson wrote: I'm getting this in a file that used to compile pre 2.11.15: Preprocessing graphical objects... programming error

2.11.15 debug help / detached beam

I'm getting this in a file that used to compile pre 2.11.15: Preprocessing graphical objects... programming error: no skylines for alignment-child continuing, cross fingers Segmentation fault I have the problem somewhat narrowed down to a couple of measures. Is there a way I can make it spit

Text crescendo collision with dynamic

This didn't used to collide in previous versions of lilypond (the last I tried this was in 2.9.24). I did a search through the bugs and didn't find anything similar. Thanks. -Jay \version 2.11.14 \paper { ragged-right = ##t }

Arpeggio collision

I see that issue 10 is closed (http://code.google.com/p/lilypond/issues/detail?id=10). However, I'm still seeing similar behavior. The attached is from the actual score. If I take out the accidentals it looks right. I can also remove the acciacatura from the low voice to keep the arpeggio on the

Crescendo extends too far.

In this example the crescendo extends to the end of the mark and no the bar line as is usual. Take the mark out and it looks fine. \version 2.11.11 \paper { ragged-right = ##t } \new Staff \relative c' { c1\ | \mark Very long

Segmentation fault 2.11.10

the last c2 is changed to a solid note (like quarter or eighth), but I still get the seg fault with a whole note. I also still got the seg fault when I changed the line to bes32[ a] c2. Am I doing anything odd or wrong? Thanks! -Jay Anderson ___ bug

Re: clef collides with rest

Ok, here's what I've come up with to show the bug a little better: - \version 2.9.21 \score { \new Staff { \relative c' { c4 c c c | c4 c8 c c4 c8 c | c8 c4 c8 c c4 c8 | c8 c c c c c c c | \times 2/3 {c4 c c} c4 c | c4 \times 2/3

Re: clef collides with rest

point you to the whole file if needed. Thanks! -Jay Anderson On 10/6/06, Graham Percival [EMAIL PROTECTED] wrote: Werner LEMBERG wrote: The bass clef in the following example collides with the rest in the following example. It looks worse in context than it does here, but normally lilypond

Re: clef collides with rest

By 'better' I meant that it shows the problem more clearly. I haven't tweaked much at all yet. This is default Lilypond and it doesn't complain one bit about it getting too dense: - Processing `E:/cygwin/home/Jay/open-scores/DukasVillanelle/trunk/Piano.ly' Parsing... Interpreting music...

partcombine status

of the dynamics when I generate the score; a pain and still not quite what I'm wanting. Thanks for all the help! -Jay Anderson \version 2.8.3 clarinetOne = \relative c'' { \time 3/4 \key f \major r4 r c~\p | c(_\markup{\italic cresc.} d ees) | f2(\p a4 | f2 c4) | f( a c | f,) r r | R2. | r4