Re: Add point-and-click to SVG output (issue 8273045)

On 2013/04/06 09:25:57, dak wrote: I actually can't see immediately from the code how one would arrive at the grob-cause expression. Can (*func), apparently a void function (?) be made to return it by default? No clue; this involves a dark part of lilypond. void interpret_stencil_expressi

Re: suggestion: change OctavateEight name to ClefTransposition - opinions?

Hi, 2013/4/6 David Kastrup : > Marc Hohl writes: >> I'd prefer ClefTransposition over ClefShift, since the latter >> implies some shift relative to the clef's default position. > > I think I'd like ClefModifier. Something like > > `clefOctavation' (integer) > Add this much extra oc

Re: suggestion: change OctavateEight name to ClefTransposition -opinions?

David Kastrup wrote Saturday, April 06, 2013 10:44 PM > I think I'd like ClefModifier. Something like +1 Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Snippet broken in 2.17.14

Federico Bruni writes: > 2013/4/5 Phil Holmes > > The snippet > > http://lilypond.org/doc/v2.17/Documentation/snippets/contexts-and-engravers#contexts- > and-engravers-engravers-one_002dby_002done no longer produces > sensible output. It was broken by > http://code.google.co

Re: suggestion: change OctavateEight name to ClefTransposition - opinions?

Marc Hohl writes: > Am 05.04.2013 23:02, schrieb Janek Warchoł: >> Hi, >> >> The name "OctavateEight" doesn't have any sense - it doesn't show that >> this grob is related to the clef, and anyway the clef can be >> "transposed" by any amount, not just an octave. >> I suggest to rename this grob t

Re: doc: explain how to add lyrics to polyphonic sections (issue 3236) (issue 8384043)

A proposal: given that no other section of 1.5.2 mentions lyrics, perhaps using my submission (or the original at 1.5.2) for temporary polyphonic context at 2.1.2 is a better option, with a link at 1.5.2 to 2.1.2? Anyone setting multi-voice music and using the examples at 1.5.2 can easily use the

Re: Stable release state

> During this two-month period, the only (non-documentation) > changes that may be made are changes that fix bugs or new ports > which do not require changes to other parts of the compiler. New > functionality may not be introduced during this period. Yes! This is what I call a f

Re: Stable release state

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Phil Holmes" > Cc: "Werner LEMBERG" ; > Sent: Saturday, April 06, 2013 3:26 PM > Subject: Re: Stable release state > > >> "Phil Holmes" writes: >> >>> At present, we're actually premature in proposing a freez

Re: Stable release state

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "Werner LEMBERG" ; Sent: Saturday, April 06, 2013 3:26 PM Subject: Re: Stable release state "Phil Holmes" writes: At present, we're actually premature in proposing a freeze to make ready for a release candidate. We

Re: Stable release state

David Kastrup wrote Saturday, April 06, 2013 10:07 AM > it is clear that master has stopped being suitable for turning into a > stable branch. There are several ways forward, none of them > particularly endearing. > > a) cut the stable branch before the last batch of changes and accumulate > o

Re: Stable release state

"Phil Holmes" writes: > At present, we're actually premature in proposing a freeze to make > ready for a release candidate. We have a number of outstanding > critical bugs and regressions which need fixing before we go anywhere > with a new stable release. So, currently, step one is to reduce t

Re: Stable release state

- Original Message - From: "David Kastrup" To: "Werner LEMBERG" Cc: Sent: Saturday, April 06, 2013 3:08 PM Subject: Re: Stable release state Werner LEMBERG writes: Declare a feature freeze for a few weeks, with only trivial additions and fixes for regressions and documentation is

Re: Stable release state

Werner LEMBERG writes: >>> Declare a feature freeze for a few weeks, with only trivial >>> additions and fixes for regressions and documentation issues. >> >> The time for a formal decision was too late, the more active >> developers informally agreed to try and nobody bothered actually >> doing

Re: Stable release state

>> Declare a feature freeze for a few weeks, with only trivial >> additions and fixes for regressions and documentation issues. > > The time for a formal decision was too late, the more active > developers informally agreed to try and nobody bothered actually > doing so. Hmm. We discussed that,

Re: Stable release state

Werner LEMBERG writes: >> Any option I forgot here? > > Declare a feature freeze for a few weeks, with only trivial additions > and fixes for regressions and documentation issues. The time for a formal decision was too late, the more active developers informally agreed to try and nobody bothered

Re: Stable release state

> Any option I forgot here? Declare a feature freeze for a few weeks, with only trivial additions and fixes for regressions and documentation issues. And *no* development branch (except private ones). This should enforce all parties to concentrate on the release, together with proper testing.

New Job

Dear all, As you might have noticed, I got quiet a while ago. The main reasons were that I have recently startet at a new job with the Austrian Financial Market Authority, adn that my focus in my spare time has also shifted away from creating scores to performing and to developing plugins for

Re: Stable release state

Hi, 2013/4/6 David Kastrup : > master has stopped being suitable for turning into a > stable branch. There are several ways forward, none of them > particularly endearing. [] > Developers simply can't be interested in doing and not doing what would > be important for a stable release. The mi

Re: Stable release state

"m...@mikesolomon.org" writes: > On 6 avr. 2013, at 12:07, David Kastrup wrote: > >> >> With the recent batch of material with missing documentation, extensive >> code changes and new functionality without previous exposure and moving >> interfaces (like >> commit 88d306d9c5666b5ade4a136df29cca

Re: Stable release state

On 6 avr. 2013, at 12:07, David Kastrup wrote: > > With the recent batch of material with missing documentation, extensive > code changes and new functionality without previous exposure and moving > interfaces (like > commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7 > Author: Mike Solomon > Date

Re: point-and-click in SVG

2013/4/3 Graham Percival > The archives show a few half-hearted attempts to get this working, > but no actual patches other than Mike's "lily dances" patch from > Dec 2010 which wasn't merged. > > I've got a patch which adds point-and-click, > https://codereview.appspot.com/8273045 > Hi Graham

Re: Add point-and-click to SVG output (issue 8273045)

https://codereview.appspot.com/8273045/diff/2001/scm/output-svg.scm File scm/output-svg.scm (right): https://codereview.appspot.com/8273045/diff/2001/scm/output-svg.scm#newcode545 scm/output-svg.scm:545: (if close-link This code is too horrible to contemplate. Setting a global variable in this

Stable release state

With the recent batch of material with missing documentation, extensive code changes and new functionality without previous exposure and moving interfaces (like commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7 Author: Mike Solomon Date: Sat Apr 6 09:54:58 2013 +0200 Break slurs between alte

PATCHES - Countdown for April 6th 2013

Hello, *Countdown – April 8th 2013 – 19:00 GMT* * * * * * * * * 1698 Defect Mike Solomon Push Slurs and ties are not