input/regression/page-layout-manual-position.lycontains:
\paper {
...
annotatespacing = ##f
annotatepage = ##t
annotateheaders = ##t
}
The first line there should be
annotate-spacing=##f
but the other two lines are real properties. Shouldn't they be
annotate-{page,headers} , to keep i
I'm trying to learn about two-pass spacing so I can add it to the
manual. How am I supposed to use the example file? When I run it for
the first time ("lilypond page-layout-twopass.ly"), it produces a
page-layout-twopass-page-layout.ly
file, but when I run lilypond again, it just produces anot
spark:~/aaa/opus/op1/out gperciva$ lilypond-book --version
File
"/Users/gperciva/Apps/LilyPond.app/Contents/Resources/bin/lilypond-
book", line 1268
found = dict ((t, None) for t in types)
^
SyntaxError: invalid syntax
(in case you're not looking at this in
On Thu, Jun 08, 2006 at 11:53:16PM -0700, Graham Percival wrote:
> Cameron, you can delete
> 2.8
> "Subproperties, like the details field of Slur and Tie may now be tuned
> with \override. [This obviously belongs in Section 9, but I don't
> understand it enough to say more!]"
> (I've documented t
On 9-Jun-06, at 1:50 AM, Cameron Horsburgh wrote:
I hear and obey...
Please note that I started working on the system start delimiter and
put it away hoping it'd make more sense in the morning. I also tried
to get the text direction thingo documented, but I couldn't get it to
work, even wit
On Fri, Jun 09, 2006 at 01:56:33AM -0700, Graham Percival wrote:
>
> On 9-Jun-06, at 1:50 AM, Cameron Horsburgh wrote:
>
> >I hear and obey...
> >
> >Please note that I started working on the system start delimiter and
> >put it away hoping it'd make more sense in the morning. I also tried
> >t
Graham Percival schreef:
spark:~/aaa/opus/op1/out gperciva$ lilypond-book --version
File
"/Users/gperciva/Apps/LilyPond.app/Contents/Resources/bin/lilypond-book",
line 1268
found = dict ((t, None) for t in types)
^
SyntaxError: invalid syntax
(in case you'r
Joe Neeman schreef:
Here are the final differences between my working copy and CVS lilypond.
To use the new page breaker, add "Page_turn_engraver" to the staff which
is relevant for page turns, then add
#(define page-breaking ly:optimal-breaking)
to your (book-wide) paper block. Page turns will
Graham Percival schreef:
input/regression/page-layout-manual-position.lycontains:
\paper {
...
annotatespacing = ##f
annotatepage = ##t
annotateheaders = ##t
}
The first line there should be
annotate-spacing=##f
but the other two lines are real properties. Shouldn't they be
annotate-
Graham Percival schreef:
Everybody else, do any of the below items need to be in the docs? If
so, please write something for them, because I don't understand them.
This is the last call; if nobody writes something for these soon, we'll
remove them from the TODO list. (Actually, even if someb
Graham Percival schreef:
Han-Wen, is there any estimate on when the new bug database will be
online? If it's going to be a long time off, I could start running my
own bug tracker, just so that I have something to do with all the bug
reports. We could figure out how to transfer that data to yo
Joe Neeman wrote:
...
(Note: this page-breaker doesn't support break-before. Use \pageBreak or
\noPageBreak at the end of the previous score instead)
Great, since break-before was introduced because you previously couldn't use
\pageBreak at the end of a score.
Will it be also be possible
On 9-Jun-06, at 4:37 AM, Mats Bengtsson wrote:
Joe Neeman wrote:
...
(Note: this page-breaker doesn't support break-before. Use \pageBreak
or
\noPageBreak at the end of the previous score instead)
Great, since break-before was introduced because you previously
couldn't use
\pageBreak at
On Fri, 2006-06-09 at 12:18 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman schreef:
> > Here are the final differences between my working copy and CVS lilypond.
> > To use the new page breaker, add "Page_turn_engraver" to the staff which
> > is relevant for page turns, then add
> >
> > #(define page-
Graham Percival wrote:
On 9-Jun-06, at 4:37 AM, Mats Bengtsson wrote:
Joe Neeman wrote:
...
(Note: this page-breaker doesn't support break-before. Use
\pageBreak or
\noPageBreak at the end of the previous score instead)
Great, since break-before was introduced because you previously
c
On Fri, 2006-06-09 at 13:37 +0200, Mats Bengtsson wrote:
>
> Joe Neeman wrote:
>
> >...
> >(Note: this page-breaker doesn't support break-before. Use \pageBreak or
> >\noPageBreak at the end of the previous score instead)
> >
> >
> Great, since break-before was introduced because you previously
On 9-Jun-06, at 3:19 AM, Han-Wen Nienhuys wrote:
Graham Percival schreef:
input/regression/page-layout-manual-position.lycontains:
\paper {
...
annotatespacing = ##f
annotatepage = ##t
annotateheaders = ##t
}
The first line there should be
annotate-spacing=##f
but the other two lines
Cameron Horsburgh wrote:
That will just leave a few things from 2.6. I gave up trying to figure out the Grid Lines.
The grid lines can't be that complicated. The grid-lines.ly example in
Regression Test
seems to examplify all you need to know, even though the example
probably can
be simplif
Graham Percival wrote:
# String arguments for music functions may be specified without #
marks. Now, \clef and \bar are also music functions.
This doesn't really need any documentation, but it means that we can replace
lots of #" by " throughout the manual and examples. However, within a
\
Hello, all --
Per the thread on the user list... Has the code for Staff.instr
changed between 2.6 and 2.8 -- specifically, \set Staff.instr does
not appear to work after the music has begun, e.g.
\relative
{
\set Staff.instr = "one"
c d e f g
On Fri, Jun 09, 2006 at 02:01:49PM +0200, Mats Bengtsson wrote:
>
>
> Cameron Horsburgh wrote:
>
> >That will just leave a few things from 2.6. I gave up trying to figure out
> >the Grid Lines.
> The grid lines can't be that complicated.
Hmm. Maybe I'm just too simple? ;-) I can have another
Cameron Horsburgh wrote:
I don't think we were so worried about adding arrows to specific spanners
(that's easy)--I was wondering what objects could have arrows attached using
this functionality. IIRC Graham thought the answer to this question might be
more appropriate in the Program Refer
Hi,
Related to Cameron's question on which objects can get an arrow by
setting the arrow property, I thought that it was just to look up which
interface contained the property -> line-spanner-interface, and then to
look up which grobs implement this interface and it turned out that
I only found G
Hi,
in the definition of TextSpanner (and several other grobs) in scm/
define-grobs.scm
or is it rather that the arrow property is missing from the
definition of the
text-spanner-interface in lily/text-spanner.cc?
Might the same type of thing (missing interface link) explain the
problem I
On Fri, Jun 09, 2006 at 02:58:43PM +0200, Mats Bengtsson wrote:
>
>
> Cameron Horsburgh wrote:
>
> >
> Do you mean that it should be possible to browse from an arbitrary property
> and find links back to all objects that implement the interface that
> includes
> that property? This is just one
Graham Percival wrote:
Sorry, I was unclear. I've changed annotate-spacing in the example,
but annotatepage and annotateheaders are lilypond properties without
hyphens. If changing them is as simple of doing "sed
/s/annotatepage/annotate-page/ * -r" I could do it, but I'm not
comfortable
Kieren MacMillan wrote:
Hi,
in the definition of TextSpanner (and several other grobs) in scm/
define-grobs.scm
or is it rather that the arrow property is missing from the
definition of the
text-spanner-interface in lily/text-spanner.cc?
Might the same type of thing (missing interface
Mats Bengtsson schreef:
I'm not sure how to correct this. Is it just that the
line-spanner-interface is missing
in the definition of TextSpanner (and several other grobs) in
scm/define-grobs.scm
yes.
text-spanner.cc calls Line_spanner::line_stencil()
--
Han-Wen Nienhuys - [EMAIL PROTECTED
Kieren MacMillan schreef:
Hello, all --
Per the thread on the user list... Has the code for Staff.instr changed
between 2.6 and 2.8 -- specifically, \set Staff.instr does not appear to
work after the music has begun, e.g.
\relative
{
\set Staff.instr = "one"
c d e f
Graham Percival schreef:
Sorry, I was unclear. I've changed annotate-spacing in the example, but
annotatepage and annotateheaders are lilypond properties without
hyphens. If changing them is as simple of doing "sed
/s/annotatepage/annotate-page/ * -r" I could do it, but I'm not
comfortable
Hi, Han-Wen:
Yes, this has been changed. The instrument name is now spanner -
which makes interactions with braces and brackets at the system
start simpler.
A wonderful benefit!
Probably the best way is to modify instrument-name-engraver.cc to
start a
new InstrumentName if the instr prop
On Monday 05 June 2006 01:48, Han-Wen Nienhuys wrote:
> Erik Sandberg schreef:
> > I have GS_LIB=
> > "/home/erik/lily/gub/gub/target/linux/system/usr/bin/../share/ghostscript
> >/8.50/lib:
> > /home/erik/lily/gub/gub/target/linux/system/usr/bin/../share/ghostscript/
> >8.50/Resource"
>
> that's re
Erik Sandberg schreef:
On Monday 05 June 2006 01:48, Han-Wen Nienhuys wrote:
Erik Sandberg schreef:
I have GS_LIB=
"/home/erik/lily/gub/gub/target/linux/system/usr/bin/../share/ghostscript
/8.50/lib:
/home/erik/lily/gub/gub/target/linux/system/usr/bin/../share/ghostscript/
8.50/Resource"
that'
On Friday 09 June 2006 15:57, Kieren MacMillan wrote:
> Hi, Han-Wen:
> > Probably the best way is to modify instrument-name-engraver.cc to
> > start a
> > new InstrumentName if the instr property changed from a previous
> > value.
>
> Sounds pretty easy... to mess up if you don't know C++... ;-)
>
OK, I submitted a patch.
/Mats
Han-Wen Nienhuys wrote:
Mats Bengtsson schreef:
I'm not sure how to correct this. Is it just that the
line-spanner-interface is missing
in the definition of TextSpanner (and several other grobs) in
scm/define-grobs.scm
yes.
text-spanner.cc calls Line_span
On 9-Jun-06, at 3:29 AM, Han-Wen Nienhuys wrote:
Graham Percival schreef:
# Generic music functions may now also be used on articulations and
chord elements
you can write a music function and do
this will run myMusicFunction on the ArticulationEvent for -.
Could somebody (not on the d
On 9-Jun-06, at 3:29 AM, Han-Wen Nienhuys wrote:
new things is: you can put in a Scheme procedure now,
\override Stem #'thickness = #(lambda (grob)
(if (= UP (ly:grob-property grob 'direction))
2.0
5.0))
Cool!
You can also combine rules like that with "grob closure". H
On 9-Jun-06, at 2:12 AM, Cameron Horsburgh wrote:
Graham:
New chapter? Oooh...
It's not online yet.
Could you remind me which parts are relatively new? I did find a
couple of typos in some newer stuff a day or so ago but I didn't do
anything about it. I'm happy to go through the newer stuf
A few months ago, we discussed being able to set these items in the
normal lilypond way, ie
\paper {
#(set-paper-size "a4")
paper-size = "a4" % proposed new method
}
#(set-global-staff-size 14)
\paper {
global-staff-size = #14 % proposed new method
}
I'm working on the new chapt
39 matches
Mail list logo
