-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 6. September 2009 08:56:22 schrieb Joseph Wakeling:
> because I've been
> having trouble building the docs proper: I always end up with an error,
>
> Output written on collated-files.pdf (40 pages, 168642 bytes).
> Transcript written on col
Reinhold Kainhofer wrote:
> It might help to look into said log file... Usually, the error messages
> towards
> the end will tell you something about the problem.
I'm not sure how to interpret what's there -- presumably that only a
subset of the intended output has been written to collated-files
On Sun, Sep 06, 2009 at 09:20:25AM +0200, Reinhold Kainhofer wrote:
> Am Sonntag, 6. September 2009 08:56:22 schrieb Joseph Wakeling:
> > because I've been
> > having trouble building the docs proper: I always end up with an error,
Sorry to belabor the point, but are you **certain** that you've
do
On Sun, Sep 06, 2009 at 09:30:06AM +0200, Joseph Wakeling wrote:
> Reinhold Kainhofer wrote:
> > It might help to look into said log file... Usually, the error messages
> > towards
> > the end will tell you something about the problem.
>
> I'm not sure how to interpret what's there -- presumably
Carl Sorensen wrote Sunday, September 06, 2009 3:46 AM
On 9/5/09 7:12 PM, "Graham Percival"
wrote:
Hmm. This could be a meaningless semantic quibble, or it could
be
something that's fundamental to the docs, GLISS, and development
in general. Is a change to the autobeaming, done via
\over
Carl Sorensen wrote Saturday, September 05, 2009 2:13 PM
On 9/5/09 1:13 AM, "Trevor Daniels" wrote:
No. It's much easier to write documentation
than it is to add commands. I would not want to
delay useful additions to the documentation or to
put off a keen documentation writer simply becaus
Thanks Joe - applied and pushed to origin/master.
The attached patch still had DOS endings, no problem with that,
but it lacked a commit message and your email address, so I
had to add those. Your previous method of creating patches
included these in the patch. Could you use that method in futu
Le dimanche 06 septembre 2009 à 09:30 +0200, Joseph Wakeling a écrit :
> I'm not sure how to interpret what's there -- presumably that only a
> subset of the intended output has been written to collated-files.pdf?
As Graham pointed out, you didn't paste the relevant part of the log,
but the error
I've finally got around to thinking about the introduction to
parallel voices in the Learning Manual - currently sections 3.2.1
and 3.2.2. You'll remember the many discussions about the two
constructs - explicit voices and the \\ construct, and the
final agreement to introduce explicit voices f
"Trevor Daniels" writes:
> I've finally got around to thinking about the introduction to parallel
> voices in the Learning Manual - currently sections 3.2.1 and 3.2.2.
> You'll remember the many discussions about the two constructs -
> explicit voices and the \\ construct, and the
> final agreeme
Hi all,
> \\ is quite more convenient than explicit voices and thus an important
> idiom that makes Lilypond friendlier to the user.
Yes, but as previously discussed, the confusion it (ultimately) causes is a
poor trade-off. The whole problem would be solved if \\ Did The Right Thing,
i.e.
<<
Hi all,
please review this patchset, which is based on my former changes:
http://codereview.appspot.com/115065
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: Reinhold,
Message:
On 2009/09/01 12:04:52, Reinhold wrote:
I can't really judge the internals of the patch. But at least I don't
see any
obvious problem.
It should be harmless, since it's basically the same code lifted from
dynamic-engraver.cc with a slight refinement for the warn
Reviewers: Reinhold,
Message:
On 2009/09/01 11:41:15, Reinhold wrote:
LGTM. But a regtest is missing ;-)
Ah, that was just me being lazy. :)
I'll add a regtest when I commit the patch.
I'm wondering whether adjacent-hairpins needs a convert rule. I'm
thinking not, since it's an internal pro
OK, I think I've cracked the problem of patches with Thunderbird. The
problem is that Thunderbird takes .patch files to be of mime-type
text/x-diff. Renaming the file to end in .txt changes its opinion of
the file type and allows the patch to be in base64 encoding.
See: http://wiki.winehq.org/Gi
Hi Patrick,
I recently noticed that /input/regression/bookparts.ly gives the warning
"Missing stencil expression: utf-8-string" what I think is related to
your patchset.
Could you please have a look at this?
Thanks,
Michael
___
lilypond-devel maili
Hi all,
Hmm... was there any progress since July on this topic?
I'd like to year if there's anything new... ;)
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Joseph Wakeling wrote Sunday, September 06, 2009 10:36 PM
OK, I think I've cracked the problem of patches with Thunderbird.
The
problem is that Thunderbird takes .patch files to be of mime-type
text/x-diff. Renaming the file to end in .txt changes its opinion
of
the file type and allows th
Trevor Daniels wrote:
> This information is undeniably useful, but I'm not sure it should
> be part of the *LilyPond* Notation Reference. We haven't included
> external references like this elsewhere, yet the Stone and Read books
> are very general and useful to all kinds of musical notation.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 6. September 2009 23:19:18 schrieb n.putt...@gmail.com:
> Reviewers: Reinhold,
>
> Message:
>
> On 2009/09/01 11:41:15, Reinhold wrote:
> > LGTM. But a regtest is missing ;-)
>
> Ah, that was just me being lazy. :)
>
> I'll add a regtest wh
Joseph Wakeling wrote:
> the duplication of two @nodes called 'Further reading' may break the doc
> build -- just checking that now.
... which the attached patch should fix.
From 39edf10a51e70a8fd07a4655b540b4194b713236 Mon Sep 17 00:00:00 2001
From: Joseph Wakeling
Date: Mon, 7 Sep 2009 01:39:31
On 2009-09-06, Michael Käppler wrote:
> Hi Patrick,
> I recently noticed that /input/regression/bookparts.ly gives the
> warning "Missing stencil expression: utf-8-string" what I think is
> related to your patchset.
> Could you please have a look at this?
Thanks, I will look at this shortly. I ha
On Sun, Sep 06, 2009 at 11:22:42PM +0100, Trevor Daniels wrote:
>
> Joseph Wakeling wrote Sunday, September 06, 2009 10:36 PM
>
>> This probably _is_ something which should be in the docs as it's not
>> something you would imagine would be a solution.
>
> Could you let me have a suitable form of wo
On 2009-09-06, Patrick McCarty wrote:
> On 2009-09-06, Michael Käppler wrote:
> > Hi Patrick,
> > I recently noticed that /input/regression/bookparts.ly gives the
> > warning "Missing stencil expression: utf-8-string" what I think is
> > related to your patchset.
> > Could you please have a look at
24 matches
Mail list logo
