Re: Determining location of the staff lines

Carl Sorensen writes: > On 2/14/10 9:38 AM, "Eric Knapp" wrote: > >> On Wed, Feb 10, 2010 at 8:58 PM, Carl Sorensen wrote: >> >>> You're making great sense. =A0This is *really* easy, once you understand = >> how >>> LilyPond engravers work. >>> >> >> I think I'm still missing a few pieces. >

Re: Life of a Grob

On Wed, Feb 17, 2010 at 11:21 PM, Carl Sorensen wrote: > I stumbled across your "Life of a Grob" feature while I was looking up stuff > on Figured Bass. > > That would be a nice feature story for the Report... :) I'll see if

Re: Determining location of the staff lines

On Thu, Feb 18, 2010 at 8:54 AM, David Kastrup wrote: >> I think it's not yet possible to do this in a Scheme engraver. >> >> Han-Wen indicated that it could be done here: >> >> http://lists.gnu.org/archive/html/lilypond-devel/2010-01/msg00594.html >> >> But I don't think it's been implemented ye

Re: Determining location of the staff lines

Han-Wen Nienhuys writes: > On Thu, Feb 18, 2010 at 8:54 AM, David Kastrup wrote: > >>> I think it's not yet possible to do this in a Scheme engraver. >>> >>> Han-Wen indicated that it could be done here: >>> >>> http://lists.gnu.org/archive/html/lilypond-devel/2010-01/msg00594.html >>> >>> But I

Re: Can't build today's git pull

On Wed, Feb 17, 2010 at 11:24 PM, Peter Chubb wrote: >>> /usr/src/lilypond/scripts/build/out/help2man out/convert-ly > >>> out/convert-ly.1 out/convert-ly:341: Warning: 'as' will become a >>> reserved keyword in Python 2.6 File "out/convert-ly", line 341 >>> except InvalidVersion as ex: ^ SyntaxEr

Re: new smaller installers to test

On Thu, Feb 18, 2010 at 2:13 AM, Han-Wen Nienhuys wrote: > On Fri, Feb 12, 2010 at 4:57 PM, Graham Percival > wrote: >> I've tweaked the list of dirs to remove from >> share/ghostscript/Resources.  The resulting files are (on average) 5 >> megs smaller.  linux-x86 works here for me. > > It looks

Re: Can't build today's git pull

Am Donnerstag, 18. Februar 2010 19:31:06 schrieben Sie: > On Wed, Feb 17, 2010 at 11:24 PM, Peter Chubb wrote: > >>> /usr/src/lilypond/scripts/build/out/help2man out/convert-ly > > >>> out/convert-ly.1 out/convert-ly:341: Warning: 'as' will become a > >>> reserved keyword in Python 2.6 File "out/

Re: Life of a Grob

On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote: > > > On 2/17/10 4:53 PM, "Joe Neeman" wrote: > > > > > I don't really make use of it anymore, since I've become familiar enough > > with the source that it isn't really useful. But it should still work > > (there is a regression test, gr

Re: Can't build today's git pull

On Thu, Feb 18, 2010 at 07:47:24PM +0100, Reinhold Kainhofer wrote: > > I won't pretend to know how python 2.4, 2.5, 2.6, 3.0 and 3.1 all > > treat this syntax, so could somebody who knows python take a look at > > the current convert-ly and make it work on 2.4.5 and up? > > From the docs at pytho

Re: Can't build today's git pull

On Thu, Feb 18, 2010 at 11:14 AM, Graham Percival wrote: > On Thu, Feb 18, 2010 at 07:47:24PM +0100, Reinhold Kainhofer wrote: >> > I won't pretend to know how python 2.4, 2.5, 2.6, 3.0 and 3.1 all >> > treat this syntax, so could somebody who knows python take a look at >> > the current convert-l

Re: Issue 659: alternate segno symbol (issue181144)

n.putt...@gmail.com schrieb: Hi Marc, LGTM, though I still think this is a lot of effort for a very obscure and little-used symbol. Perhaps it is little-used because it was missing in lilypond? ;-) Or do you think this is just too much and we should forget about it all? (I don't hope so, becau

[PATCH] Web: add @bugfixes macro.

Okay to push? - Mark From 32559c85c69db1681205c9f9fe7ae2a46703e873 Mon Sep 17 00:00:00 2001 From: Mark Polesky Date: Thu, 18 Feb 2010 11:53:58 -0800 Subject: [PATCH] Web: add @bugfixes macro. This also fixes several broken/incorrect links. --- Documentation/common-macros.itexi |9 +

Re: Life of a Grob

On 2/18/10 11:58 AM, "Joe Neeman" wrote: > On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote: > > You need to be running a lilypond binary that was compiled with > --enable-debugging for it to work. I've been doing that., but thanks for the tip. > Also, the regtest doesn't produce > a

Re: Life of a Grob

On Thu, 2010-02-18 at 13:46 -0700, Carl Sorensen wrote: > > > On 2/18/10 11:58 AM, "Joe Neeman" wrote: > > > On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote: > > > > You need to be running a lilypond binary that was compiled with > > --enable-debugging for it to work. > > I've been doi

Re: Can't build today's git pull

> "Graham" == Graham Percival writes: Graham> On Wed, Feb 17, 2010 at 11:24 PM, Peter Chubb Graham> wrote: /usr/src/lilypond/scripts/build/out/help2man out/convert-ly > out/convert-ly.1 out/convert-ly:341: Warning: 'as' will become a reserved keyword in Python 2.6 File "out/co

\sustainOff

I want to create a sustain-pedal-signature longer then the last note. \set Staff.pedalSustainStyle = #'mixed c\sustainOn c c c s1 s8 % r1 r8 \sustainOff This works fine with rests but doesn't work with spacer rests. Could somebody change it in a way, that the example works with rests AND with s

Re: \sustainOff

On 2/18/10 3:52 PM, "Werner" wrote: > I want to create a sustain-pedal-signature longer then the last note. > > \set Staff.pedalSustainStyle = #'mixed > c\sustainOn > c c c > s1 s8 > % r1 r8 > \sustainOff > > This works fine with rests but doesn't work with spacer rests. You can make this work

spacer rests and grace notes

Sometimes I use \once \override NoteHead #'transparent = ##t \grace c1 to get an „anchor“ for something, which is invisible and doesn't disturb the bar-count. It would be easier, if spacer rest would be accepted as grace-notes. \grace s4 But they aren't. ___

Re: spacer rests and grace notes - OK

> It would be easier, if spacer rest would be accepted as grace-notes. > But they aren't. Sorry - it seems they are. I think, I had trouble, because I didn't read the hint: „Grace note synchronization can also lead to surprises. Staff notation, such as key signatures, bar lines, etc., are also

doc - add link

In http://lilypond.org/doc/v2.13/Documentation/notation-big-page.en.html#Rehearsal-marks one can read: „For common tweaks to the positioning of rehearsal marks, see Formatting text.“ Please add: [see Formatting text] and Aligning Objects using the break-alignable-interface as a link to http://lil

Re: new smaller installers to test

On Thu, Feb 18, 2010 at 4:43 PM, Graham Percival wrote: > woah, this is weird.  The 2.13.12 regtest comparison shows them just fine: > http://lilypond.org/test/v2.13.12-1/compare-v2.13.11-1/index.html > (you can see the hiragana in utf-8.ly) > > the 2.13.13 regest doesn't show them changing: > htt

Re: new smaller installers to test

On Thu, Feb 18, 2010 at 11:25:33PM -0200, Han-Wen Nienhuys wrote: > On Thu, Feb 18, 2010 at 4:43 PM, Graham Percival > wrote: > > woah, this is weird.  The 2.13.12 regtest comparison shows them just fine: > > The regtest comparison uses the bounding boxes inside lilypond. > Errors in ghostscript d

Re: new smaller installers to test

On Fri, Feb 19, 2010 at 4:51 AM, Graham Percival wrote: > On Thu, Feb 18, 2010 at 11:25:33PM -0200, Han-Wen Nienhuys wrote: >> The largest ones are the Encoding files, which are related to >> international fonts, so if this is the cause of the problem (I think >> it is). > > ok, I'll test that whe