Graham Percival wrote Saturday, September 12, 2009 12:20 PM
On Sat, Sep 12, 2009 at 09:34:35AM +0100, Trevor Daniels wrote:
Graham Percival wrote Saturday, September 12, 2009 12:00 AM
It was not deliberate to change the docs lnie-width.
I that case I'd like to change it back.
No
On Sun, Sep 13, 2009 at 09:14:48AM +0100, Trevor Daniels wrote:
Graham Percival wrote Saturday, September 12, 2009 12:20 PM
It appears to be a side effect of some other change to
lilypond-book,
which I suspect now picks up 'smallbook' rather than 'A4' for ly
fragments.
It -is- due to
Sorry, silly me. :)
I think we're nearly there. I'm just about to do a regtest check just
to be sure.
Just a few remaining nitpicks:
- trailing spaces
- long lines
That should be fixed now.
Is there a default for maximum line length?
Regards,
Michael
From
On 9/13/09 4:41 AM, Michael Käppler xmichae...@web.de wrote:
Sorry, silly me. :)
I think we're nearly there. I'm just about to do a regtest check just
to be sure.
Just a few remaining nitpicks:
- trailing spaces
- long lines
That should be fixed now.
Is there a default
Op zaterdag 12-09-2009 om 09:27 uur [tijdzone +0200], schreef John
Mandereau:
Le samedi 12 septembre 2009 à 02:54 +0100, Graham Percival a écrit :
I now have a core2 quad with 4 gigs at my desk. Unfortunately the
building is locked over the weekend, but on Monday I can seriously
tackle
Le dimanche 13 septembre 2009 à 06:45 -0600, Carl Sorensen a écrit :
80 characters maximum; I generally try to keep the lines about 70
characters.
FWIW in Python code it's often hard to keep lines below 80 characters,
so I try to keep them around 80 characters and require them to be less
than
Le dimanche 13 septembre 2009 à 09:44 +0100, Graham Percival a écrit :
Is lilypond-book affected by the macro expansions?
I assumed it was, but perhaps not.
Here, let's do a quick test. Add an @afourpaper to one of the
manuals, but not the others. Wait a day, then see how they both
On Sun, Sep 13, 2009 at 03:44:00PM +0200, John Mandereau wrote:
Le dimanche 13 septembre 2009 à 09:44 +0100, Graham Percival a écrit :
Here, let's do a quick test. Add an @afourpaper to one of the
manuals, but not the others. Wait a day, then see how they both
look on kainhofer.
This
Hi Neil,
There are some subtle spacing changes in the docs, but no breakages:
quite often the line width is slightly shorter, resulting in tighter
spacing (see the PNG for expressive-headword.ly attached, which is
eleven pixels shorter than the current example on kainhofer.com).
now I know
Hi Jan,
In my current attempt to build LilyPond with GUB, I hit a name clash in
netpbm, patch attached. I hate languages without namespaces or
equivalent concept :-)
Best,
John
From 030efb393486e5717e74dc91b9b145020ab7b014 Mon Sep 17 00:00:00 2001
From: John Mandereau john.mander...@gmail.com
Op zondag 13-09-2009 om 16:33 uur [tijdzone +0200], schreef John
Mandereau:
Hi John,
In my current attempt to build LilyPond with GUB, I hit a name clash in
netpbm, patch attached. I hate languages without namespaces or
equivalent concept :-)
Applied. Thanks!
Jan.
--
In message blu149-w35f4018afa3162e0a4ceba94...@phx.gbl, Kieren
MacMillan kieren_macmil...@sympatico.ca writes
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
2009/9/13 Michael Käppler xmichae...@web.de:
That should be fixed now.
Thanks, it's applied.
Is there a default for maximum line length?
I tend to follow Carl's suggestion for 80 columns, but as John's
pointed out, sometimes it's awkward to keep within this limit.
Regards,
Neil
2009/9/13 Michael Käppler xmichae...@web.de:
now I know what's the reason. The attempt I made with line-width-cropping
doesn't really work,
since if there are several \paper blocks line-width-cropping affects all and
breaks the other settings.
Ah, I see.
Apart from this, the only other
On 13.09.2009, at 17:59, Anthony W. Youngman wrote:
Using partcombine, I think it's doing its job properly. But the
result is a mass of a2, Solo I, Solo II which I don't want.
I'd like both parts printed in full, with only a2 where they're
both playing the same.
I haven't tried it, but
Graham Percival wrote Sunday, September 13, 2009 2:49 PM
That said, I could have done the same mistake as you did a week
ago by
moving @afourpaper to macros.itexi :-P
Ok, I'll move them out.
Thanks Graham - that will fix it. I'd have spotted
this sooner if I'd looked at learning.tely :(
Neil Puttock wrote Sunday, September 13, 2009 7:45 PM
2009/9/13 Michael Käppler xmichae...@web.de:
Btw. I don't understand, why lilypond-book inserts no line-width
value when
called with fragment.
What is the reason for this behaviour?
I'm not sure, to be honest.
I think
Hi Neil,
Thanks, it's applied.
Great. The next step is attached. Can you please run a regtest?
Regards,
Michael
From 2aa0ede53ec2b8e03f47c3b0f525cfbc636c Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?= xmichae...@web.de
Date: Sun, 13 Sep 2009 22:11:36 +0200
Subject:
I think lilypond-book inserts line-width only when 'quote' or
'lilyquote' is specified (or 'linewidth' itself, of course).
I don't think so. Look at lilypond-book.py:951. This value preserves if
no option is set. You can verify this by running this small tex file, if
you want:
In message 4aac29f2.1000...@webdrake.net, Joseph Wakeling
joseph.wakel...@webdrake.net writes
I'm then entering these details into a Google Docs spreadsheet (which
I'll share with anyone who requests it). The same spreadsheet also
contains a complete list of contributors (from Francisco's
In message f12b2646-e12b-47ae-94aa-3e52294d7...@googlemail.com, James
E. Bailey derhindem...@googlemail.com writes
On 13.09.2009, at 17:59, Anthony W. Youngman wrote:
Using partcombine, I think it's doing its job properly. But the result is a
mass of a2, Solo I, Solo II which I don't want.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 13. September 2009 23:22:04 schrieb Anthony W. Youngman:
If it hasn't been done, it sounds like it would be a good idea to try
and combine the voice combining and part combining code with switches to
say how much should be
Anthony W. Youngman wrote:
I think you don't understand copyright properly ...
DON'T track whether they support switching the licence. Because if
they do, they will (presumably already) have switched the licence on
their contributions.
... but we have no records of that switch, because
In message 200909140024.50780.reinh...@kainhofer.com, Reinhold
Kainhofer reinh...@kainhofer.com writes
Am Sonntag, 13. September 2009 23:22:04 schrieb Anthony W. Youngman:
If it hasn't been done, it sounds like it would be a good idea to try
and combine the voice combining and part combining
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 14. September 2009 00:00:28 schrieb Anthony W. Youngman:
DON'T track whether they support switching the licence. Because if
they do, they will (presumably already) have switched the licence on
their contributions.
I don't think so. Many
In message 4aad7567.5060...@webdrake.net, Joseph Wakeling
joseph.wakel...@webdrake.net writes
Thanks nevertheless for your useful suggestions -- I hope this email
clears up what I do and don't intend. I'll update the licensing part of
the spreadsheet accordingly.
Sounds good.
Best wishes,
Hi Reinhold, Wol, et al:
I've been thinking about implementing something like that myself
(basically
controlling combined/split voices via context properties,
overriding the bad
choices the partcombiner makes).
What say we make a serious effort at rewriting the partcombiner from
the
In message blu0-smtp76a410ac3d24e8496e9aaa94...@phx.gbl, Kieren
MacMillan kieren_macmil...@sympatico.ca writes
Hi Reinhold, Wol, et al:
I've been thinking about implementing something like that myself
(basically
controlling combined/split voices via context properties,
overriding the bad
In message 200909140059.35325.reinh...@kainhofer.com, Reinhold
Kainhofer reinh...@kainhofer.com writes
Am Montag, 14. September 2009 00:00:28 schrieb Anthony W. Youngman:
DON'T track whether they support switching the licence. Because if
they do, they will (presumably already) have switched the
On Sun, Sep 13, 2009 at 8:29 PM, Anthony W. Youngman
lilyp...@thewolery.demon.co.uk wrote:
So your idea is basically postponing the problem to a time, where we might
not
be able to solve it properly any more?
Nope. My idea is basically saying let's face reality. Some people will
never agree
On Sun, Sep 13, 2009 at 09:36:47PM -0300, Han-Wen Nienhuys wrote:
Please don't speak for me. I am not opposed to GPL v3, but I don't
want to be involved in any of the legal (or
laymen-people-interpreting-law) and bikeshedding discussions that this
'upgrade' has to involve. Ie. please reach
31 matches
Mail list logo
