Re: Make tab-note-heads and fretboards use common code. (issue186268)

I've found a bug in this code that showed up with the latest changes in the regression tests. I'll have a new patch set later; don't spend any time on this one right now. THanks, Carl http://codereview.appspot.com/186268/show ___ lilypond-devel

Re: Make tab-note-heads and fretboards use common code. (issue186268)

I've found a bug in this code that showed up with the latest changes in the regression tests. I'll have a new patch set later; don't spend any time on this one right now. THanks, Carl http://codereview.appspot.com/186268/show ___ lilypond-devel

Re: [PATCH]: New G clef

On 1/23/10 3:19 AM, "Marc Hohl" wrote: > Carl Sorensen schrieb: >> Marc Hohl has worked on a new G clef that is rotated about 1.5 degrees >> clockwise to improve its balance, as suggested by Jan >> >> (see >> ) >> >> A 120

Re: Make tab-note-heads and fretboards use common code. (issue186268)

OK, so I added the optional default to ly:context-property, and fixed the indentation. make check works. I think it's good to go now. http://codereview.appspot.com/186268/diff/1/7 File scm/translation-functions.scm (right): http://codereview.appspot.com/186268/diff/1/7#newcode236 scm/transla

Re: Consistency in \context block formatting

On Thu, Jan 28, 2010 at 01:01:16AM -, Trevor Daniels wrote: > > Graham Percival wrote Wednesday, January 27, 2010 6:43 PM > >> I'm happy with having a newline there, but please glance over the >> LM stuff you wrote, and confirm that you prefer it with a newline. >> I'll get James to make the ap

Re: Consistency in \context block formatting

Graham Percival wrote Wednesday, January 27, 2010 6:43 PM On Wed, Jan 27, 2010 at 06:12:14PM -, Trevor Daniels wrote: Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM There's nothing in the documentation policy for \context block formatting, The patch is being written by James

Re: Latest git (lilypond-translation) build fail

On Wed, Jan 27, 2010 at 10:33:45PM +0100, Harmath Dénes wrote: > Latest revision in lilypond-translation branch gives the following build > error when running make all: > > make PACKAGE=LILYPOND package=lilypond -C ly-examples all && make > PACKAGE=LILYPOND package=lilypond -C server all && tru

Latest git (lilypond-translation) build fail

Latest revision in lilypond-translation branch gives the following build error when running make all: make PACKAGE=LILYPOND package=lilypond -C ly-examples all && make PACKAGE=LILYPOND package=lilypond -C server all && true true make: *** server: No such file or directory. Stop. make[2]: *** [

Re: How to do this correctly?

2010/1/27 Carl Sorensen : > I don't think there is a way to do this better as the code sits now.  The > accidentals in the ambitus are AmbitusAccidentals, and are create by the > Ambitus_engraver, so the standard accidental styles (which might do what you > want) don't apply. Agreed. I think you

Re: How to do this correctly?

On 1/27/10 11:59 AM, "David Kastrup" wrote: > > > The following does what I _want_ but looks more like an accident than > anything else. > > \new Voice \with { \consists "Ambitus_engraver" } > { \key des\major \set keySignature = #'() des' d'' } > > What I want is the ambitus to be engrave

How to do this correctly?

The following does what I _want_ but looks more like an accident than anything else. \new Voice \with { \consists "Ambitus_engraver" } { \key des\major \set keySignature = #'() des' d'' } What I want is the ambitus to be engraved without signature. Working with \override Ambitus #'keySignature

Re: Consistency in \context block formatting

On Wed, Jan 27, 2010 at 06:12:14PM -, Trevor Daniels wrote: > > Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM >> >> There's nothing in the documentation policy for \context block >> formatting, The patch is being written by James Lowe. >> I much prefer the context name to be on the n

Re: Consistency in \context block formatting

Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM There's nothing in the documentation policy for \context block formatting, but since you've amended some examples in the LM, I thought I'd check what the preferred style should be to prevent any confusion. I much prefer the context name

Consistency in \context block formatting

Hi Graham, There's nothing in the documentation policy for \context block formatting, but since you've amended some examples in the LM, I thought I'd check what the preferred style should be to prevent any confusion. I much prefer the context name to be on the next line (this is how I've always e

Re: GUB buiding from a local source tree?

Op donderdag 14-01-2010 om 09:49 uur [tijdzone -0500], schreef Boris Shingarov: > But right now, we are not even there, as even simply building the > current official head from the main lilypond repository, does not work. > It hangs when trying to download from the standard url: Why do you th

Baselines from lilypond-book?

Hi, when one uses lilypond-book for LaTeX imaging and places music fragments inline, the baseline of the music fragment is the bottom of the image. That's a nuisance since the fragments will not line up with anything sensible in the same line. Is it possible to have Lilypond pass baseline inform