David Nalesnik writes:
> On Sat, Feb 4, 2017 at 7:02 PM, David Nalesnik
> wrote:
>> Yes, I've run it a number of times.
>>
>> All I can think is that somewhere during the upload process I lose my
>> authenticated connection with www.google.com.
>>
>> Hmmm. I've rebased everything to a single c
Hi folks,
I just stumbled over a bug with \displayLilyMusic and scheme-engravers.
The following fails in recent devel:
%%%
\version "2.19.55"
\displayLilyMusic \new Staff \with {
\consists #(lambda (context)
(make-engraver))
} \relative { bes'4 a c b }
%%%
ERROR: In proced
Hello,
Here is the current patch countdown list. The next countdown will be on
February 8th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
5039 Replace \set Staff.instrumentName with \with form in doc exa
The problem with "mentoring" this is that the expertise for successfully
mentoring this project is the same as for doing it yourself. This is
not a question of making a plan and then implementing its parts over the
course of several weeks.
Either an idea works or not. And it needs to be tied a
Jan-Peter Voigt writes:
> Hi folks,
>
> I just stumbled over a bug with \displayLilyMusic and
> scheme-engravers. The following fails in recent devel:
>
> %%%
>
> \version "2.19.55"
>
> \displayLilyMusic \new Staff \with {
> \consists #(lambda (context)
>(make-engraver))
> } \re
Jan-Peter Voigt writes:
> Hi folks,
>
> I just stumbled over a bug with \displayLilyMusic and
> scheme-engravers. The following fails in recent devel:
>
> %%%
>
> \version "2.19.55"
>
> \displayLilyMusic \new Staff \with {
> \consists #(lambda (context)
>(make-engraver))
> } \re
David Kastrup writes:
> Jan-Peter Voigt writes:
>
>> Hi folks,
>>
>> I just stumbled over a bug with \displayLilyMusic and
>> scheme-engravers. The following fails in recent devel:
>>
>> %%%
>>
>> \version "2.19.55"
>>
>> \displayLilyMusic \new Staff \with {
>> \consists #(lambda (context)
>>
Am 5. Februar 2017 15:21:54 MEZ schrieb d...@gnu.org:
>The problem with "mentoring" this is that the expertise for
>successfully
>mentoring this project is the same as for doing it yourself. This is
>not a question of making a plan and then implementing its parts over
>the
>course of several wee
Hi David,
Am 05.02.2017 um 16:19 schrieb David Kastrup:
David Kastrup writes:
Jan-Peter Voigt writes:
Hi folks,
I just stumbled over a bug with \displayLilyMusic and
scheme-engravers. The following fails in recent devel:
%%%
\version "2.19.55"
\displayLilyMusic \new Staff \with {
\co
Hi all,
I'm somewhat worried about LilyPond's GSoC project proposals list. Right
now I'm purging the web page
(http://lilypond.org/google-summer-of-code.html) from projects without
mentors, and I have the feeling when this process is completed we're
left with an unsatisfactory state.
>From the 9
Hi Urs,
Am 06.02.2017 um 00:24 schrieb Urs Liska:
Hi all,
I'm somewhat worried about LilyPond's GSoC project proposals list. Right
now I'm purging the web page
(http://lilypond.org/google-summer-of-code.html) from projects without
mentors, and I have the feeling when this process is completed
Am 6. Februar 2017 07:56:34 MEZ schrieb Jan-Peter Voigt :
>Hi Urs,
>
>
>Am 06.02.2017 um 00:24 schrieb Urs Liska:
>> Hi all,
>>
>> I'm somewhat worried about LilyPond's GSoC project proposals list.
>Right
>> now I'm purging the web page
>> (http://lilypond.org/google-summer-of-code.html) from pro
> So essentially per now we will have only 4/5 projects left:
>
> * Improving internal chord structure
> * Adopting SMuFL
> * Adding glyph variants
> * openLilyLib testing and documentation
>
> I find this list quite disappointing, and I'm afraid it won't be
> terribly attractive to poten
13 matches
Mail list logo
