Nice job!
And I have to second Carl's comment: The `compromise' stuff is the
best one $(Q#|(B and perhaps you can make a compromise between the `orig'
stuff and `compromise' w.r.t. the shape of the down-flags...
Werner
___
lilypond-devel maili
On 1/29/11 4:14 PM, "Janek Warchoł"
wrote:
> Hi,
>
> After some discussion in "flags, beams and stem length in forced
> directions - output improvement" thread, i've created new flags for
> shorter-stemmed notes and new rules for shortening stems. Please look
> at pdfs linked below and tell m
Hi,
After some discussion in "flags, beams and stem length in forced
directions - output improvement" thread, i've created new flags for
shorter-stemmed notes and new rules for shortening stems. Please look
at pdfs linked below and tell me what you think.
Changes:
- stem length transition between
This patch solves Neil's problem with clef spacing.
LGTM.
Carl
http://codereview.appspot.com/4095041/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2011/01/26 18:18:21, Graham Percival wrote:
Neil has identified a potential downside to this patch.
That was a restoration of 2.12.3 behavior, which I had mentioned in the
original email thread but didn't explicitly handle until now.
Status of this patch is
1)revert ee0488, which was a glob
Mike Solomon ufl.edu> writes:
>
> It seems that the variable `measures' is unused in this function - can this
> be
deleted?
>
Who are you asking? git blame ("git credit" would have been a nicer name)
shows these lines have not been touched in several years, so it is not likely
to be in a
On Jan 29, 2011, at 1:21 PM, Han-Wen Nienhuys wrote:
> On Sat, Jan 29, 2011 at 1:37 PM, m...@apollinemike.com
> wrote:
>
>>
>> Hey Hanwen,
>> What you describe above is close-ish to what I wound up putting in my newest
>
> I don't think so, since the main scoring loops still loop through all
>
On Sat, Jan 29, 2011 at 8:45 AM, Carl Sorensen wrote:
>
> On 1/29/11 6:20 AM, "Graham Percival" wrote:
>
>> On Fri, Jan 28, 2011 at 11:19:10PM -0800, Patrick McCarty wrote:
>>> I meant to post this to -devel a while ago, but I opened a Github
>>> tracker issue for GUB.
>>> https://github.com/jann
On Sat, Jan 29, 2011 at 1:37 PM, m...@apollinemike.com
wrote:
>
> Hey Hanwen,
> What you describe above is close-ish to what I wound up putting in my newest
I don't think so, since the main scoring loops still loop through all
combinations in no particular order.
I looked closer at your example
On 1/29/11 6:20 AM, "Graham Percival" wrote:
> On Fri, Jan 28, 2011 at 11:19:10PM -0800, Patrick McCarty wrote:
>> I meant to post this to -devel a while ago, but I opened a Github
>> tracker issue for GUB.
>> https://github.com/janneke/gub/issues#issue/2
>
> Interesting. How do I get a prop
On Jan 29, 2011, at 10:50 AM, Marc Hohl wrote:
> Am 29.01.2011 09:50, schrieb David Kastrup:
>> Marc Hohl writes:
>>
>>> If this is done similar to LaTeX packages where you can enable the
>>> option "draft"
>>> to speed up compiling, and if everything looks ok, you remove the draft and
>>> that'
Am 29.01.2011 09:50, schrieb David Kastrup:
Marc Hohl writes:
If this is done similar to LaTeX packages where you can enable the
option "draft"
to speed up compiling, and if everything looks ok, you remove the draft and
that's it, then this would be not too confusing for users.
draft Mode in
On Jan 29, 2011, at 10:10 AM, Han-Wen Nienhuys wrote:
> On Fri, Jan 28, 2011 at 11:55 AM, m...@apollinemike.com
> wrote:
>>> Despite the joke, this is a semi-serious suggestion that I've been
>>> hoping that somebody might be interested in for years. There's a
>>> bunch of options that we can en
On Fri, Jan 28, 2011 at 11:55 AM, m...@apollinemike.com
wrote:
>> Despite the joke, this is a semi-serious suggestion that I've been
>> hoping that somebody might be interested in for years. There's a
>> bunch of options that we can enable or disable to change the
>> amount of processing power; i
http://codereview.appspot.com/4022045/diff/14001/input/regression/beam-collision.ly
File input/regression/beam-collision.ly (right):
http://codereview.appspot.com/4022045/diff/14001/input/regression/beam-collision.ly#newcode17
input/regression/beam-collision.ly:17: g,,,8[ \clef treble d''8]
newl
> LGTM; please send me a git-format origin patch and I'll push it.
thanks!
p
0001-regtest-and-changes-for-mensural-ligature-improvemen.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman
Reviewers: Graham Percival,
Message:
All fixed. New patchset uploaded.
http://codereview.appspot.com/4022045/diff/12001/input/regression/beam-collision.ly
File input/regression/beam-collision.ly (right):
http://codereview.appspot.com/4022045/diff/12001/input/regression/beam-collision.ly#newco
On 2011/01/29 14:07:20, benko.pal wrote:
and a try at Changes.
LGTM; please send me a git-format originpatch and I'll push it.
http://codereview.appspot.com/3989049/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mai
Reviewers: ,
Message:
and a try at Changes.
Description:
enhance ligature test with new features
Please review this at http://codereview.appspot.com/3989049/
Affected files:
M Documentation/changes.tely
M input/regression/mensural-ligatures.ly
___
LGTM.
http://codereview.appspot.com/4022045/diff/12001/input/regression/beam-collision.ly
File input/regression/beam-collision.ly (right):
http://codereview.appspot.com/4022045/diff/12001/input/regression/beam-collision.ly#newcode15
input/regression/beam-collision.ly:15: \clef bass g,,,8[ \clef
Bernard Hurley writes:
> On Sat, Jan 29, 2011 at 09:46:23AM +0100, Marc Hohl wrote:
>> What about something like
>> \draftModeOn / \draftModeOff ?
>>
>
> How about four named modes:
>
> "Screen" mode - Fastest but good enough for checking on screen. Useful
> if lily is being used as a composition
On Fri, Jan 28, 2011 at 11:19:10PM -0800, Patrick McCarty wrote:
> I meant to post this to -devel a while ago, but I opened a Github
> tracker issue for GUB.
> https://github.com/janneke/gub/issues#issue/2
Interesting. How do I get a proper git format-patch version of
this? The raw link gives me
Hi
On Fri, Jan 28, 2011 at 11:14:56PM -0800, Dennis Raddle wrote:
> I am completely new to LilyPond, but it seems like a good way to get
> beautiful notation, and, I hope, experiment with playback algorithms that
> add human touch. What I wonder is whether the Scheme extension language
> would let
On Sat, Jan 29, 2011 at 09:46:23AM +0100, Marc Hohl wrote:
> What about something like
> \draftModeOn / \draftModeOff ?
>
How about four named modes:
"Screen" mode - Fastest but good enough for checking on screen. Useful if lily
is being used as a composition tool.
"Draft" mode - Not that beauti
Hi Graham,
I haven't forgotten this patch but unfortunately I don't seem to find
time to fix it at the moment. It seems as if two patches got mixed up
at least. So I'm probably not responsible for the good stuff! ;-(
I can't promise but I'll try to take care of it next weekend.
Thanks,
patr
Right,
I will have a look at that.
Thanks!
Felipe
On 28 January 2011 12:17, wrote:
> Hi Felipe,
>
> I'm very sorry about the delay, but at least I'm looking at it now, and
> I'll take care of badgering people to review it once it's ready.
>
> Unfortunately due to the delay, we have a few extr
Marc Hohl writes:
> If this is done similar to LaTeX packages where you can enable the
> option "draft"
> to speed up compiling, and if everything looks ok, you remove the draft and
> that's it, then this would be not too confusing for users.
draft Mode in LaTeX omits details but does not change
Am 28.01.2011 20:42, schrieb Han-Wen Nienhuys:
On Fri, Jan 28, 2011 at 4:43 PM, Graham Percival
wrote:
On Fri, Jan 28, 2011 at 04:18:16PM -0200, Han-Wen Nienhuys wrote:
On Fri, Jan 28, 2011 at 11:43 AM, Graham Percival
wrote:
lilypond -p 0 my_file.ly% for quick work
lilypond -p 2 m
28 matches
Mail list logo
