On 4/11/06, Graham Percival <[EMAIL PROTECTED]> wrote:
> (this'll probably get lost while HWN is away, but anyway...)
>
> From the docs,
> "A hairpin starts at the left edge of the beginning note and ends on
> the right edge of the ending note."
>
> tupletFullLength (boolean)
> If set, t
Since \espressivo is a hack of cresc/decr, it should be below the staff
by default (currently it is not). How would I change scm/script.scm to
fix this?
("espressivo" .
((avoid-slur . around)
(quantize-position . #t)
(script-stencil . (feta . ("espr" . "espr")))
(s
> > ** [2.6] Newly created staves and lyric lines, can be put in any
> > vertical order, by setting alignBelowContext or alignAboveContext
> > properties in the newly created context. An example of the use of this
> > is in input/regression/alignment-order.ly. [It's hard to say if this
> > needs to
On 11-Apr-06, at 4:36 PM, Cameron Horsburgh wrote:
The List
** [2.6] Newly created staves and lyric lines, can be put in any
vertical order, by setting alignBelowContext or alignAboveContext
properties in the newly created context. An example of the use of this
is in input/regression/
(this'll probably get lost while HWN is away, but anyway...)
From the docs,
"A hairpin starts at the left edge of the beginning note and ends on
the right edge of the ending note."
tupletFullLength (boolean)
If set, the tuplet is printed up to the start of the next note.
Could we
Howdy folks,
I've been going through the NEWS files to see if there's anything that
still needs documenting. I've come up with a couple of draft lists and
discussed them with Graham Percival, and I now have a list of things we
agree need to go in. We've already documented some but we don't have th
> From: Graham Percival <[EMAIL PROTECTED]>
> Subject: State of the docs, April 2006
> To: lily-devel
> I'm getting burnt out from trying to do all the documentation. In
> addition, in a fit of insanity I agreed to be the new Bug Meister.
Don't burn yourself by doing too much, my friend!
> INST
Graham Percival wrote:
>
> On 11-Apr-06, at 2:51 PM, Cameron Horsburgh wrote:
>
>> Graham Percival wrote:
>>> This link still works
>>> http://lilypond.org/doc/v2.9/Documentation/
>> That link works, but the link to the User Manual doesn't. Has Han-Wen
>> taken it with him?
>
> Eh? The link fro
We have a bunch of "make clean"; what's the right sequence of commands
to get the cleanest possible CVS tree? Currently I'm doing
make web-clean
make clean
make cvs-clean
Is that correct? Should distclean be in there? Would it be possible
to have a single "make all-clean" command?
Cheers,
> INSTRUMENT-SPECIFIC NOTATION
> Lilypond knowledge required: moderate knowledge in a specific area
> Estimated time: variable
Since I've done a lot of worker on choral music already, I'd be happy
to work on that particular area.
Geoff
___
lilypond-de
On 11-Apr-06, at 2:51 PM, Cameron Horsburgh wrote:
Graham Percival wrote:
This link still works
http://lilypond.org/doc/v2.9/Documentation/
That link works, but the link to the User Manual doesn't. Has Han-Wen
taken it with him?
Eh? The link from that page to the User Manual certainly work
Graham Percival wrote:
>
> On 11-Apr-06, at 2:22 PM, Cameron Horsburgh wrote:
>
>> The 2.9 manual seems to have disappeared off the web--the link just
>> points back to the doc index. If somebody's borrowed it, could you
>> please put it back?
>
> This link still works
> http://lilypond.org/doc/
On 4/11/06, Erlend Aasland <[EMAIL PROTECTED]> wrote:
> On 4/11/06, Marcus Macauley <[EMAIL PROTECTED]> wrote:
>
> >
> >> Thanks for the proofs. FWIW I think the very last one -- at 50% of a
> >> single staffspace -- is perfect. The distinction between 52.5% and 50%
> >> is particularly fine, but
Hi all,
I'm getting burnt out from trying to do all the documentation. In
addition, in a fit of insanity I agreed to be the new Bug Meister. To
give me time to do the Bug stuff, we need more people working on the
docs. I also have major doc changes that I've wanted to make for
almost a yea
On 11-Apr-06, at 2:22 PM, Cameron Horsburgh wrote:
The 2.9 manual seems to have disappeared off the web--the link just
points back to the doc index. If somebody's borrowed it, could you
please put it back?
This link still works
http://lilypond.org/doc/v2.9/Documentation/
but it's for the 2.9.
Hi folks,
The 2.9 manual seems to have disappeared off the web--the link just
points back to the doc index. If somebody's borrowed it, could you
please put it back?
Cam
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailma
On Tue, 11 Apr 2006 22:31, Geoff Horton wrote:
> > I don't know if that information helps at all, but at least it provides
> > some sort of motivation for the behaviour. In any case, I would vote for
> > changing it too.
>
> But what if a person wants to refer to a Scheme variable (as in the
> poi
On 4/4/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> The choice for GUILE is mostly historical, and I'm all for switching to
> Mz, but I fear that such a move involves a tremendous amount of work,
> due to API differences.
>
> You're welcome to give an Mz port a try, if you think it's feasible
> Probably the best thing would be to make real options for the
> variables people actually want to set often.
I can't argue with that in principle, but the more I read on this
list, the more I realize that Lily is used for many different styles
and to many different ends. Determining who the "peo
On 4/11/06, Geoff Horton <[EMAIL PROTECTED]> wrote:
> But what if a person wants to refer to a Scheme variable (as in the
> point-and-click example)? I agree it's far from ideal, but I think
> switching to auto-quoting arguments would break more than it solves.
Probably the best thing would be to
> Without having looked at the code, I'd say that the reason is that the
> argument gets parsed as a scheme value. So if you say -dpaper-size=HELLO,
> that is equivalent to having
> #(set-default-paper-size HELLO)
> in your file. But of course you want something like
> #(set-default-paper-size "HEL
On 4/11/06, Marcus Macauley <[EMAIL PROTECTED]> wrote:
>> Thanks for the proofs. FWIW I think the very last one -- at 50% of a>> single staffspace -- is perfect. The distinction between 52.5% and 50%>> is particularly fine, but I vote for 50%.
I actually would vote for 55%.I agree with Marcus that
Hi,
On Tue, 11 Apr 2006, Jan Nieuwenhuizen wrote:
> I currently have very little time to work on Lily related stuff.
That's a pity.
> I have a daytime job, two small twin girls and just bought a house :-)
Congratulations!
Ciao,
Dscho
___
lilypon
David Feuer writes:
> I've written code to do rounded polygons /properly/ in both PostScript
> and SVG. The SVG was a bit tricky because SVG doesn't have
> PostScript's arct. I would greatly appreciate some help changing the
> code in lookup.cc to match my new drawing procedures.
That's great.
On 11-Apr-06, at 12:45 AM, Cameron Horsburgh wrote:
Hmm. I've nailed down the syntax, but the -d flag seems to be able to
take a whole range of parameters, and I'm not sure if we really need to
list this as a specific instance.
I already considered this. :)
I think it's worth it. We alread
On Tue, 11 Apr 2006 17:19, Cameron Horsburgh wrote:
> Joe Neeman wrote:
> >> ERROR: Unbound variable: a5
> >
> > -dpaper-size=\"letter\" works for me. But it seems as though
> > -dpaper-size=letter would be the better way. Is there a reason it doesn't
> > work this way?
>
> Good question. Using the
Cameron Horsburgh wrote:
> Hi folks,
>
> I'm in the process of writing up some of the previously undocumented
> features in the NEWS files. I'm having a bit of trouble with this comment:
>
> **
> The default paper size may now be set from the command line using
> -dpaper-size.
> *
Joe Neeman wrote:
>> ERROR: Unbound variable: a5
> -dpaper-size=\"letter\" works for me. But it seems as though
> -dpaper-size=letter would be the better way. Is there a reason it doesn't
> work this way?
>
Good question. Using the quotes isn't that obvious, and escaping them
even less so. I'l
28 matches
Mail list logo
