Re: priority problem \fermataMarkup vs. text markup

>>> Hmm.  I currently can't imagine a situation where a value > 0 is >>> needed, so I vote to remove the setting of >>> #'outside-staff-priority for MultiMeasureRestText -- however, I'm >>> not sure whether this has any influence to issue #495 (this looks >>> rather unrelated to #'outside-staff-pr

Re: making a book with LilyPond

Federico, Put the \include "english.ly" call in your top-level file instead (see below) Cheers, Ian Federico Bruni wrote: Hi Jan, thanks for your reply. Actually, I had tried \bookpart (see the 1st example below, in my first email) but I have problems with \include. If in the included f

Re: hairpin followed by text crescendo is too long

2009/8/31 Neil Puttock : > I'll have a patch ready once I've done a regtest check. OK, no breakages to report, so here's a patch: http://codereview.appspot.com/110122/show Regards, Neil test-hairpin.pdf Description: Adobe PDF document ___ lilypond-d

Re: New markup command `parenthesize'

2009/8/11 Thomas Morgan : > Thank you, and thanks for the comments!  Here are two addenda > to the original patch that make the improvements you suggested: Excellent, thank you. I fear this is in danger of being ignored though since it's a bit awkward to review properly; can you squash everythin

Re: hairpin followed by text crescendo is too long

2009/8/31 Reinhold Kainhofer : > Attached is an example where a hairpin, which is immediately followed by a > text crescendo, is too long. > if a hairpin is followed by another hairpin, it is shortened (to the middle of > the note instead of the end), but this does not happen for text crescendi. I

Re: Flageolett articulation above and below a chord (i.e. double articulations are discarded)

2009/8/31 Reinhold Kainhofer : > I'll create a snippet for the LSR. Thanks, I've tagged it as a docs snippet. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Flageolett articulation above and below a chord (i.e. double articulations are discarded)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 31. August 2009 22:06:47 schrieb Neil Puttock: > 2009/8/31 Reinhold Kainhofer : > > Unfortunately, I'm unable to produce this in lilypond at all. Only the > > first articulation of each type is assigned. All further ones are > > ignored. Sam

Re: Flageolett articulation above and below a chord (i.e. double articulations are discarded)

2009/8/31 Reinhold Kainhofer : > Unfortunately, I'm unable to produce this in lilypond at all. Only the first > articulation of each type is assigned. All further ones are ignored. Sample > file is attached Don't forget you can stick scripts (like fingerings) inside a chord via the New_fingering_

Flageolett articulation above and below a chord (i.e. double articulations are discarded)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently typesetting several excepts from Dvorak's Cello concert, and in one place (end of the second movement), there are two two-note chords with a flageolett above and below the chord (one \flageolet for each of the two notes). Unfortunately

Re: Docs build failure

2009/8/31 Reinhold Kainhofer : > ideally it should not be there, but I have now fixed this by setting the > output-suffix to "1" and then clearing it. This produces the same file names > as > before, so that all scripts will continue working. Cheers. I should have mentioned there's also a copy

Re: Docs build failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 31. August 2009 16:52:01 schrieb Neil Puttock: > 2. using ly:format in make-ps-images causes scaling of PNGs to fail > for multi-page snippets: [...] > Here's the line which formats the filename for each PNG: > > 113 (pngn (format

Re: Docs build failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 31. August 2009 18:54:10 schrieb Reinhold Kainhofer: > Am Montag, 31. August 2009 16:52:01 schrieb Neil Puttock: > > 1. ouput-count doesn't work, > > Or rather, we don't need output-count any more! > > > which causes the regression test > >

Re: Docs build failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 31. August 2009 16:52:01 schrieb Neil Puttock: > 1. ouput-count doesn't work, Or rather, we don't need output-count any more! > which causes the regression test > clip-systems.ly to fail: > > 82 \markup { \epsfile #X #30.0 #(format

hairpin followed by text crescendo is too long

Attached is an example where a hairpin, which is immediately followed by a text crescendo, is too long. if a hairpin is followed by another hairpin, it is shortened (to the middle of the note instead of the end), but this does not happen for text crescendi. Similarly, a hairpin following another

Docs build failure

Hi everybody, I've just tried to do a clean build, and there are two problems related to some recent patches: 1. ouput-count doesn't work, which causes the regression test clip-systems.ly to fail: 82 \markup { \epsfile #X #30.0 #(format #f "~a-1-from-2.0.1-to-4.0.1-clip.eps" (ly:parser-ou

Re: [PATCH] Improve `make distclean' behavior

Le lundi 31 août 2009 à 10:16 +0200, John Mandereau a écrit : > Le dimanche 30 août 2009 à 16:05 -0700, Patrick McCarty a écrit : > > Attached is a patch that modifies `make distclean' so that it behaves > > correctly. > > > > Okay to apply? BTW please no longer spend too much time on a build syst

Re: [PATCH] Improve `make distclean' behavior

Le dimanche 30 août 2009 à 16:05 -0700, Patrick McCarty a écrit : > Attached is a patch that modifies `make distclean' so that it behaves > correctly. > > Okay to apply? LGTM. Sorry for my current absence in Lily development, but I'm busy with setting up a joint supervision for my PhD. Greetings