On 2 August 2011 10:28, Phil Holmes m...@philholmes.net wrote:
So any bug in Lily that produces bad output can never be High? Or - to put
it another way, we, the developers ,only regard bugs as high when they
hinder us, not when they make you, the user's life difficult. I don't like
that.
Hi James
Needs a bit more work along the lines suggested by Janek. This is quite
a tricky concept, and a little more explanation would help here
(although maybe not quite as verbose as Janek's helpful explanation -
leave out the musical bits :)
Also, you can't just delete the unwanted snippets
http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/4837050/diff/1/Documentation/notation/rhythms.itely#newcode1638
Documentation/notation/rhythms.itely:1638: \compoundMeter
This should work now.
http://codereview.appspot.com/4807053/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
lily/text-interface.cc updated.
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
James, you wrote Thursday, August 04, 2011 11:55 AM
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of tdanielsmu...@googlemail.com
)Sent: 04 August 2011 09:32
)Also, you can't just delete the unwanted snippets from the git
tree -
)they'll reappear at the next LSR
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: James Lowe james.l...@datacore.com; tdanielsmu...@googlemail.com
Cc: Lily-Devel List lilypond-devel@gnu.org
Sent: Thursday, August 04, 2011 2:46 PM
Subject: Re: Doc: Added \compoundMeter function to NR (issue4837050)
Hi,
I think I found a proper way to calculate church rests.
I also updated so that it applies on the latest git HEAD.
Bertrand.
http://codereview.appspot.com/4536068/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Sorry, sent this to -user by accident. Should be in -devel
-- Weitergeleitete Nachricht --
Betreff: fixcc.py and variable assignments on two lines
Datum: Donnerstag, 4. August 2011, 17:04:58
Von: Reinhold Kainhofer reinh...@kainhofer.com
An: LILYPOND Mailinglist
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Tuesday, August 02, 2011 8:09 PM
Subject: Re: Quick way to recreate docs
On Tue, Aug 02, 2011 at 07:48:14PM +0100, Phil Holmes wrote:
-
Reinhold Kainhofer wrote Thursday, August 04, 2011 4:40 PM
fixcc.py seems to mess up indentation of variable assignments that
are spread
over two lines. In particular, if you have
static char const *WARRANTY
= _i (This program is free software; you can redistribute it
and/or\n
then
Le 04/08/2011 17:58, Phil Holmes disait :
[...]
OK. To me, the ability to have the whole document compiled and viewable
quickly would improve my (very poor) ability to write docs quite a bit.
I've now knocked up a script. It's run like:
./MakeDocScript.sh essay
to create essay.pdf. It works
Am Dienstag, 26. Juli 2011, 14:22:22 schrieb Reinhold Kainhofer:
Please review:
http://codereview.appspot.com/1659041/
I have now fixed all problems and adjusted the documentation, so the latest
patch at
http://codereview.appspot.com/1659041/
is ready for review and inclusion.
Please
On Thu, Aug 04, 2011 at 04:58:08PM +0100, Phil Holmes wrote:
Surprisingly, I get:
phil@phil-lily:~/lilypond-git/build$ touch Documentation/notation.tely
phil@phil-lily:~/lilypond-git/build$ make out=www
Documentation/out-www/notation.pdf
make: Nothing to be done for
Second Draft. Hopefully I've covered everything without being too
verbose or talking through the code.
I also found some old 'scheme' code in the glossary and so updated that
with the new \compoundMeter function instead also removed another
reference to the snippet found in world.itely.
2011/8/4 Janek Warchoł lemniskata.bernoull...@gmail.com:
Hi,
I think there is a problem with handling suspended whole notes: Lily
aligns them as if they had stems.
See attached suspended whole notes - in my opinion the last two
measures should look the same and have both chords in the same
2011/8/4 Xavier Scheuer x.sche...@gmail.com:
That has been registered as issue #1774, isn't it?
http://code.google.com/p/lilypond/issues/detail?id=1774
Not quite. Gould makes an exception for semibreves with adjacent
notes; in this case, they should be aligned as if they had stems:
\version
Reviewers: ,
Message:
This is much shorter than my previous work on this issue and is in the
spirit of Han-Wen's 6c6ae92410f087d0318a3c302eb6877cfc7fae45.
fit_factor only makes sense when applied to the middle of curves (what
we can consider their steady states). Near their attachments (what
On 2011/08/03 19:43:52, Graham Percival wrote:
cannot apply to master due to fixcc.
New patchset uploaded - should apply.
Neil - whenever you get the chance, I'd like to hear more of what you
have to say about it. If you think that custom engravers would be a
better idea here (or even
LGTM
On Thu, Aug 4, 2011 at 9:20 PM, mts...@gmail.com wrote:
Instead of defining the middle of curve in terms of curve length, I use
a constant number here. It seems to do the trick better than a variable
length.
Well, we can't pretend that there's unanimous support for this,
and of course there will always be concerns about specific
technical details... but I think we've got an ok set of guidelines
for future build system work, and it's time to start producing
patches.
Haven't heard much about this proposal, but I guess silence is a
form of consent? I'll wait a few days before moving ahead with
this, in case there's any post-final discussion.
http://lilypond.org/~graham/gop/gop_6.html
** Proposal summary
Potentially sensitive or private matters will be
22 matches
Mail list logo
