Hello,
Here is the current patch countdown list. The next countdown will be on
June 11th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push: No patches to Push.
Countdown:
1388 Support OpenType font features
Hi Dan (et al.),
> It is worth investigating the possibility of changing the part combiner from
> an event router to a property setter. If that is feasible, Kieren’s concerns
> about voice naming would still need to be addressed, but without the
> complication of the extra voices that exist on
> On Jun 7, 2017, at 19:48, Carl Sorensen wrote:
>
> On 6/7/17 5:30 PM, "Kieren MacMillan"
> wrote:
>
>>> Could it not leave the parts where they are (continuous parts in
>>> exactly one voice context per part) and change their context properties
>>> instead?
>>
>> Not sure I quite understand
On 6/7/17 5:30 PM, "Kieren MacMillan"
wrote:
>Hi Dan,
>
>> If we¹re going to ask that kind of question, let¹s mention a more
>>radical redesign.
>
>I would be happy with a "radical redesign", if that's what it takes to
>(a) solve some of the problems I face with partcombine on a daily basis,
>or
Hi Dan,
> If we’re going to ask that kind of question, let’s mention a more radical
> redesign.
I would be happy with a "radical redesign", if that's what it takes to (a)
solve some of the problems I face with partcombine on a daily basis, or (b)
establish a good base for future development/im
> On Jun 7, 2017, at 09:34, Kieren MacMillan
> wrote:
>
> As a first step, I would offer that we should figure out how (if?) the "one"
> context can be funnelled seamlessly into the "shared" and "solo" contexts —
> as I see it, that's the main problem with lyrics getting disconnected (etc.).
David,
Make sure that your main focus will be getting back into good shape.
If schedule and energy levels allow for starting of a 2.20 branch I think it
would be good to update ghostscript to a version that has the PNG-transparency
glitches fixed that surfaced in 2.19.51.
Ghostscript has made a
2017-06-07 21:53 GMT+02:00 Carl Sorensen :
>
> Is there any place else in the codebase where we include lilypond examples
> in the doc strings? It seems like we ought to try for consistency; either
> use lilypond examples in all of the doc strings (maybe at least for markup
> functions) or in non
Hi David,
> Maybe check the effects that super- and subscripts cause on a block of text?
Good thought. Doesn't seem to have a negative effect.
Other thoughts?
Or should I start moving towards a submittable patch?
Thanks,
Kieren.
Kieren MacMillan, composer
‣ web
Ok folks,
tomorrow I am leaving for physical therapy. I expect 3 weeks without
extension since the problematic areas have boiled down considerably in
the last two weeks already: swallowing is an ongoing nuisance, balance
is pretty well but looking back when bicycling still is precarious in
parti
Kieren MacMillan writes:
> Hi Carl,
>
>> You have not yet tested your baseline-skip parameter with a different
>> default-staff-size. I think that you will probably need to include the
>> default baseline-skip when determining the new baseline-skip. Font sizes
>> avoid this problem by using a s
Hi Carl,
> You have not yet tested your baseline-skip parameter with a different
> default-staff-size. I think that you will probably need to include the
> default baseline-skip when determining the new baseline-skip. Font sizes
> avoid this problem by using a scale parameter. I don't know that
On 6/7/17 2:01 PM, "Kieren MacMillan"
wrote:
>> Is there any place else in the codebase where we include lilypond
>>examples
>> in the doc strings? It seems like we ought to try for consistency;
>>either
>> use lilypond examples in all of the doc strings (maybe at least for
>>markup
>> function
Hi Carl,
Thanks for the helpful response.
> The spacing appears pretty good to me.
Excellent.
> Seems like an abstracted function with two parameters (magstep and
> baselineskip) would be about right. Of course, if you can determine
> baselineskip from magstep, you would only need one paramete
On 6/7/17 12:17 PM, "lilypond-devel on behalf of Kieren MacMillan"
wrote:
>Hello all,
>
>Thanks to some help (on the user-list) from David K, I've started to
>attack issue #3947.
>(I figured this would be a nice, relatively painless way to get my feet
>wet in the dev/git/patch process.)
>
>The sn
Hello all,
Thanks to some help (on the user-list) from David K, I've started to attack
issue #3947.
(I figured this would be a nice, relatively painless way to get my feet wet in
the dev/git/patch process.)
The snippet included below is what I have so far. It appears to work as hoped.
Two ques
On 07/06/17 00:54, Kieren MacMillan wrote:
> Hi all,
>
>> Got what?
>
> Hmmm… Looks like the list didn't accept my screenshot… =(
>
> Anyway, it was a fatal error.
> I have apparently fixed it (?) by uninstalling and doing the whole procedure
> again from scratch.
>
Dunno whether it's what yo
Reviewers: ,
Description:
Fix typos in \offset documentation
- Fix errors in description of OttavaBracket example
- Minor improvements in wording
Please review this at https://codereview.appspot.com/322040043/
Affected files (+5, -4 lines):
M Documentation/notation/changing-defaults.itely
Hi Dan,
> The part combiner can also route events to “shared”, “solo”, and “null”
> contexts. If you took the step you’re proposing, the next question would be
> why can’t a person control those other names too? If there is going to be
> user control, should it be more comprehensive?
Absolut
19 matches
Mail list logo
