> On Feb 18, 2015, at 4:35 AM, Trevor Daniels wrote:
>
> Individually comments below. Most I like, but a couple I don't.
>
> Thanks for doing this - I'm well aware of the effort involved and the
> difficulties of achieving good artistic design (usually by my failing!)
> Trevor
Hi Trevor, Tha
On 2015/02/18 19:32:57, david.nalesnik wrote:
Hmmm. Since this is no longer just a wrapper for Grob::name, I
suppose I should
rewrite it in Scheme.
Not so sure now. Error reporting options in Scheme aren't as good.
https://codereview.appspot.com/203090043/
On 2015/02/18 20:39:19, david.nalesnik wrote:
On 2015/02/18 18:12:58, david.nalesnik wrote:
> On 2015/02/18 18:08:32, david.nalesnik wrote:
>
> Putting it into Scheme will need to wait for Issue 4289 to make it
to master,
> since I'll be able to use ly:item-get-column here.
However, we lose
On 2015/02/18 18:12:58, david.nalesnik wrote:
On 2015/02/18 18:08:32, david.nalesnik wrote:
Putting it into Scheme will need to wait for Issue 4289 to make it to
master,
since I'll be able to use ly:item-get-column here.
However, we lose the nice error reporting which happens when you do
(
"Trevor Daniels" writes:
> David Kastrup wrote Wednesday, February 18, 2015 6:00 PM
>
>> More seriously, currently \displayLilyMusic deals badly with
>> { c4 c4 8 8 4 } which gets rendered as { c4 c 8 8 4 } and does
>> consequently not recreate its input. It would be rather tricky to fix
>> that
David Kastrup wrote Wednesday, February 18, 2015 6:00 PM
> More seriously, currently \displayLilyMusic deals badly with
> { c4 c4 8 8 4 } which gets rendered as { c4 c 8 8 4 } and does
> consequently not recreate its input. It would be rather tricky to fix
> that since by the time the 8 is print
Hmmm. Since this is no longer just a wrapper for Grob::name, I suppose
I should rewrite it in Scheme.
https://codereview.appspot.com/203090043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-deve
> Comment #3 on issue 4293 by lemzw...@googlemail.com: Patch: Various
> fixes/improvements in connection with Smob allocation
> https://code.google.com/p/lilypond/issues/detail?id=4293
>
> David, in such cases please proceed immediately!
+1
Trevor
_
On 2015/02/18 18:57:21, dak wrote:
On 2015/02/18 18:53:03, c_sorensen wrote:
> On 2015/02/09 23:46:45, thomasmorley651 wrote:
>
> >
> > I'd happily do it, though, why alpabetically? And why only for the
lines
with
> > \accept, could be done for the context-defs as well.
> > And it's also thinka
On 2015/02/18 18:53:03, c_sorensen wrote:
On 2015/02/09 23:46:45, thomasmorley651 wrote:
>
> I'd happily do it, though, why alpabetically? And why only for the
lines with
> \accept, could be done for the context-defs as well.
> And it's also thinkable to sort it following context-hierarchy:
On 2015/02/09 23:46:45, thomasmorley651 wrote:
I'd happily do it, though, why alpabetically? And why only for the
lines with
\accept, could be done for the context-defs as well.
And it's also thinkable to sort it following context-hierarchy: first
bottom-contexts like Voice, then Staff up to
I completely agree. Better to be accurate than visually appealing in this
regard.
- Abraham
Sent from my iPhone
> On Feb 18, 2015, at 11:00 AM, David Kastrup [via Lilypond]
> wrote:
>
>
> Hi, currently
> \displayLilyMusic { c4 c c c } produces output { c4 c c c }. I lean
> towards letti
Am 18.02.2015 um 19:00 schrieb David Kastrup:
Hi, currently
\displayLilyMusic { c4 c c c } produces output { c4 c c c }. I lean
towards letting it produce output { c4 c4 c4 c4 }. Reason: that's
what's actually in the data structures of the music. The machinery that
tries to decide when it can
On 2015/02/18 18:08:32, david.nalesnik wrote:
Putting it into Scheme will need to wait for Issue 4289 to make it to
master, since I'll be able to use ly:item-get-column here.
https://codereview.appspot.com/197690044/
___
lilypond-devel mailing list
On 2015/02/18 18:07:19, dak wrote:
On 2015/02/18 18:05:17, david.nalesnik wrote:
> On 2015/02/18 18:02:38, dak wrote:
> > On 2015/02/18 17:53:44, david.nalesnik wrote:
> > > Please review. Thanks!
> >
> > Can't this be done just as easily in Scheme?
>
> Sure--that crossed my mind. The reason I
On 2015/02/18 18:05:17, david.nalesnik wrote:
On 2015/02/18 18:02:38, dak wrote:
> On 2015/02/18 17:53:44, david.nalesnik wrote:
> > Please review. Thanks!
>
> Can't this be done just as easily in Scheme?
Sure--that crossed my mind. The reason I went with C++ is so that it
would be
documen
On 2015/02/18 18:02:38, dak wrote:
On 2015/02/18 17:53:44, david.nalesnik wrote:
> Please review. Thanks!
Can't this be done just as easily in Scheme?
Sure--that crossed my mind. The reason I went with C++ is so that it
would be documented prominently, but I could change it if that's not a
On 2015/02/18 17:53:44, david.nalesnik wrote:
Please review. Thanks!
Can't this be done just as easily in Scheme?
https://codereview.appspot.com/197690044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinf
Hi, currently
\displayLilyMusic { c4 c c c } produces output { c4 c c c }. I lean
towards letting it produce output { c4 c4 c4 c4 }. Reason: that's
what's actually in the data structures of the music. The machinery that
tries to decide when it can leave off the default duration is
potentially e
Reviewers: ,
Message:
Please review. Thanks!
Description:
Function to display the rhythmic location of a grob
A convenient way to return the musical position of a grob within
a score will be very helpful in debugging, among other uses.
This patch creates a function ly:grob-rhythmic-location w
author Paul Morris
Tue, 10 Feb 2015 02:11:19 + (21:11 -0500)
committer James Lowe
Wed, 18 Feb 2015 10:41:39 + (10:41 +)
commit 1dfeaf8fd3f2a106bdd37d3b7dc83d9168fff750
https://codereview.appspot.com/197530043/
_
Paul Morris Wednesday, February 18, 2015 6:43 AM
> I have some more changes to propose for the website. You can see two
> mock-ups at the links below (just remove the spaces in the URLs). One uses
> the current green color for the background, and in the other I tried out a
> blue background
22 matches
Mail list logo
