On Fri, 15 Aug 2008 20:47:15 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> `make all' and `make web' fail on the latest master. Here is a patch
> that fixes the issue.
Thanks, applied. Sorry about that.
It appears that the "updatedocs.sh" script on the GDP server
is even less informativ
Hi,
`make all' and `make web' fail on the latest master. Here is a patch
that fixes the issue.
Thanks,
Patrick
0001-Fix-compile.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinf
On 8/15/08 4:39 PM, "Graham Percival" <[EMAIL PROTECTED]> wrote:
> On Fri, 15 Aug 2008 08:03:15 -0600
> "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
>
>> On 8/15/08 3:25 AM, "Graham Percival" <[EMAIL PROTECTED]> wrote:
>>
>>
>> My model for the Learning Manual is that it answers the question "
On Fri, 15 Aug 2008 08:03:15 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> On 8/15/08 3:25 AM, "Graham Percival" <[EMAIL PROTECTED]> wrote:
>
> > In the LM, definitely. In the NR, these warnings might be more
> > prominent, and/or Carl's suggestion about delaying << {} \\ {}>>
> > until
I agree
Trevor
- Original Message -
From: "Carl D. Sorensen" <[EMAIL PROTECTED]>
To: "Graham Percival" <[EMAIL PROTECTED]>; "Mats Bengtsson"
<[EMAIL PROTECTED]>
Cc:
Sent: Friday, August 15, 2008 3:03 PM
Subject: Re: finished second draft?
On 8/15/08 3:25 AM, "Graham Percival" <
2008/8/15 Werner LEMBERG <[EMAIL PROTECTED]>:
>> They can usually do that if you can limit the range to a single
>> release.
>
> I've done bisecting. This is the problematic commit:
>
> commit 2b8a93c3007d1789ac67c86b0ed63fbae003fc6e
> Author: Joe Neeman <[EMAIL PROTECTED]>
> Date: Mon Aug 6
Kieren
Thanks for all your comments and suggestions so far (of which this was the
first).
The templates are now all in the LSR, so you can submit changes to them
yourself, or at least you will be able to do so when the database is back
functioning again.
Valentin, are you able to transfer
> They can usually do that if you can limit the range to a single
> release.
I've done bisecting. This is the problematic commit:
commit 2b8a93c3007d1789ac67c86b0ed63fbae003fc6e
Author: Joe Neeman <[EMAIL PROTECTED]>
Date: Mon Aug 6 13:17:21 2007 +1000
Tweak spacing between a musica
2008/8/15 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> On Fri, Aug 15, 2008 at 1:48 PM, Neil Puttock
>> - Should an unknown engraver cause compilation to fail? I was
>> wondering whether it might be better to issue a warning rather than an
>> error in get_translator ().
>
> No, in general, we should tr
On Fri, Aug 15, 2008 at 1:48 PM, Neil Puttock
> There are two related issues which I'm concerned about:
>
> - Should an unknown engraver cause compilation to fail? I was
> wondering whether it might be better to issue a warning rather than an
> error in get_translator ().
No, in general, we should
Hi,
Here's a patch which makes sure that there's a check that an engraver
exists before an attempt is made to remove it within a \with block.
There are two related issues which I'm concerned about:
- Should an unknown engraver cause compilation to fail? I was
wondering whether it might be better
make -C lily clean
On Thu, Aug 14, 2008 at 10:32 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> I've been working on tracking down the loss of functionality for
> Forbid_line_break_engraver.
>
> To do this I have to check out various commits and see if they have the
> functionality.
>
> From ti
They can usually do that if you can limit the range to a single release.
On Fri, Aug 15, 2008 at 3:26 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> > Attached are two files which show the difference. Again, I'm posting
>> > it here to the list and not to the bug tracker so that either Han-Wen
Graham Percival wrote:
I would propose to still introduce the <<{...} \\ {...} >> feature
first, but with some bells
and whistles saying that you might get problems together with lyrics
and automatic beaming
and telling where to look at that time.
In the LM, definitely. In the NR, th
Thanks for all your comments. I apologize for the confusion.
I've eliminated the workaround from the documentation.
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
2008/8/15 Carl D. Sorensen <[EMAIL PROTECTED]>:
> My model for the Learning Manual is that it answers the question "How do I
> do something?" The Notation Reference tells me "How do I solve problems
> with something in the LM?", or "How do I extend what I learned in the LM?".
>
> The shortcuts we
On 8/15/08 3:25 AM, "Graham Percival" <[EMAIL PROTECTED]> wrote:
> On Fri, 15 Aug 2008 11:03:00 +0200
> Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
>> Carl D. Sorensen wrote:
>>>
>
>> I would propose to still introduce the <<{...} \\ {...} >> feature
>> first, but with some bells
>> and whistle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 15. August 2008 schrieb Carl D. Sorensen:
> They don't show the indications in use, but in their font, the axis is
> asymmetrical -- the vertical line appears left of center of the horizontal
> line.
Gardner Read give an example of a Harp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 15 August 2008 00:21:43 you wrote:
> 2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> > Here's my attempt, which defines a \harp-pedal #"^v-|^--v" markup
> > command (plus a version, which t
I have done the reordering, please help me translating it from English
to English where necessary.
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=Documentation/user/simultaneous.itely;h=62618eb377efc8ef96a8b26837f95c2bce12da80;hb=3dab373f67842d0bf775a4cbbad3d47dd607df12
A preview of
On Fri, 15 Aug 2008 11:03:00 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Carl D. Sorensen wrote:
> >
> > We could then introduce the << \\ >> syntax as a simple way to
> > handle music where we don't care that temporary voices are created
> > and then discarded.
>
> Seriously, how many of yo
Carl D. Sorensen wrote:
Perhaps it
would be clearer if we started with single-staff polyphony with named and
explicitly created voices, along with the \voiceOne through \voiceFour
properties.
We could then introduce the << \\ >> syntax as a simple way to handle music
where we don't care that
I agree with Trevor. This is a feature, not a bug. If you search the
mailing list archives, you
will find a number of complaints and questions about the fact that you
couldn't get a line break
when the Completion_heads_engraver had split notes, even though you
normally can have a
line break if t
Carl
Why do you want a tied note to forbid a line break?
It is preferable that it permits it, surely?
Trevor
- Original Message -
From: "Carl D. Sorensen" <[EMAIL PROTECTED]>
To: "LilyPond Development"
Cc: "Han-Wen Nienhuys" <[EMAIL PROTECTED]>
Sent: Friday, August 15, 2008 3:07 AM
24 matches
Mail list logo
