Re: beam problem

2004-01-17 Thread Werner LEMBERG
> indeed, but I'm still curious about the traceback? Can you try for > me? Here it is, from CVS 2004-01-15 22:09. [`bt full' makes my gdb crash, sorry] Werner == #0 programming_error (s=0xbfffdfdc) at include/string.icc

Re: dynamic in parentheses

2004-01-17 Thread José Luis Cruz
Werner wrote: > > I need dynamic marks in parentheses, for example `(f)'. How can > this be done best with lilypond? Ideally, I would like to have this > encapsulated as a `\fpar' (or something similar), in analogy to > `\f'. > I also think it would be a good idea. Not only for dynamics, bu

dynamic in parentheses

2004-01-17 Thread Werner LEMBERG
I need dynamic marks in parentheses, for example `(f)'. How can this be done best with lilypond? Ideally, I would like to have this encapsulated as a `\fpar' (or something similar), in analogy to `\f'. Hmm, there aren't parentheses at all in the dynamics font... Werner _

Re: beam problem

2004-01-17 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > > % warnings. I wasn't able to make the example shorter; if I remove a > > > % bar, lilypond formats it within a single line (BTW, this yields an > > > % *extremely ugly* result because the spacing is squeezed to a > > > % minimum), and the error doesn't occur

Re: 2.1.10 problem

2004-01-17 Thread Heikki Johannes Junes
On Fri, 16 Jan 2004 23:46:20 +0100 (CET) Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > Here a trivial patch to make 2.1.10 compile. > > > Werner Thanks. Applied. -- Heikki Junes ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.

2.1.10 problem

2004-01-17 Thread Werner LEMBERG
Here a trivial patch to make 2.1.10 compile. Werner == --- buildscripts/lilypond.words.py.old Fri Sep 26 07:51:30 2003 +++ buildscripts/lilypond.words.py Fri Jan 16 23:41:38 2004 @@ -55,16 +55,6 @@ # more identifie

possible tuplet spanner improvement

2004-01-17 Thread Werner LEMBERG
% % This file shows a problem with tuplet spanners in lilypond % CVS 2004-01-16 22:37. % % . Since tuplet lines are far thinner than beams, the standard % quantization algorithm for vertical start and end positions gives % bad results if the slope of the spanner is small. I suggest to % inc

Re: right bearing of meter signs

2004-01-17 Thread Werner LEMBERG
> > [...] I believe that the space between a clef and a time > > signature/key signature is too big in general. > > too big at the start of the line, in the middle, or both? At the start of the line. Currently, I don't have a real-use example of the latter. Werner __

Re: rehearsal mark problems

2004-01-17 Thread Werner LEMBERG
> > The \default command to increase the rehearsal number produces > > strange results. > > Strange? You mean: you don't want the number font to be used? Well, it is strange that the `1' is (sometimes?) taken from the normal text font, and the `2', `3', ... from the number font. Funnily, after

Re: octavation bug (continued)

2004-01-17 Thread Werner LEMBERG
> > % . There must be a minimum distance between the octavation line > > % and the topmost note, not taking into account the height of > > % the closing vertical dashed line. > > I added padding in the OttavaSpanner Thanks. I'll store the remaining two bugs in my `bug database' :-) Wer

Re: beam problem

2004-01-17 Thread Werner LEMBERG
> > % . I get a lot of > > % > > % programming error: No beam posns (Continuing; cross thumbs) > > % > > % warnings. I wasn't able to make the example shorter; if I remove a > > % bar, lilypond formats it within a single line (BTW, this yields an > > % *extremely ugly* result because the

Re: harmonic note head problems

2004-01-17 Thread Werner LEMBERG
> Do harmonic heads also exist in diferent > forms for quarter/half/etc. ? No. > I have a fix in 2.1 CVS. Will test soon, thanks. Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel