Re: git-cl problem

2016-05-26 Thread Federico Bruni
Il giorno ven 27 mag 2016 alle 1:59, John Gourlay ha scritto: I believe my git-cl problem was due to an incorrect setting in my Google Account Settings. I was not allowing access by “less secure” apps as described in Contributor’s Guide, section 2.3. I wonder if the CG should be revised, becau

Re: Let define-session-public place variables natively into parser (issue 300110043 by d...@gnu.org)

2016-05-26 Thread dak
Reviewers: carl.d.sorensen_gmail.com, Message: On 2016/05/27 04:23:29, Carl wrote: Looks very nice to me. I couldn't have done it, but I love how it works. Can you elaborate on the "couldn't have done it" part? define-session-public copies some ugly code (concerning undead structures or somet

Let define-session-public place variables natively into parser (issue 300110043 by d...@gnu.org)

2016-05-26 Thread Carl . D . Sorensen
Looks very nice to me. I couldn't have done it, but I love how it works. Thanks, Carl https://codereview.appspot.com/300110043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Tie properties vs. slur properties.

2016-05-26 Thread Carl Sorensen
On 5/25/16 7:26 PM, "lilypond-devel on behalf of tisimst" wrote: > >P.S. While we're talking properties, is there anyone who'd be willing to >make the trill spanner squiggle "~" externally \override-able independent >of the trill text "tr"? Interestingly enough, the trill spanner squiggle is a

Re: git-cl problem

2016-05-26 Thread John Gourlay
I believe my git-cl problem was due to an incorrect setting in my Google Account Settings. I was not allowing access by “less secure” apps as described in Contributor’s Guide, section 2.3. I wonder if the CG should be revised, because it implies that “allowed” is the default, but in my case the

Re: Tie properties vs. slur properties.

2016-05-26 Thread Carl Sorensen
On 5/25/16 7:26 PM, "lilypond-devel on behalf of tisimst" wrote: >What's the benefit of nesting properties like this? I'm open to hearing >arguments for it, but why not have them all accessible at top-level? Is it >programmatically beneficial to have some properties in the "details" >alist? >I w

Re: Tie properties vs. slur properties.

2016-05-26 Thread tisimst
On Thu, May 26, 2016 at 12:50 AM, David Kastrup [via Lilypond] < ml-node+s1069038n190980...@n5.nabble.com> wrote: > tisimst <[hidden email] > > writes: > > > On Wed, May 25, 2016 at 12:19 AM, Werner LEMBERG [via Lilypond] < > > [hidden email] <