Re: Branch management

Am 12.08.2016 um 07:21 schrieb littlesincanada: > Hi, > > On 11/08/16 21:18, David Kastrup wrote: >> littlesincanada writes: >> >>> On the face of it, a rebase is the obvious solution, but I'm told that >>> it's a cardinal sin to rebase commits that have already

Re: Branch management

Hi, On 11/08/16 21:18, David Kastrup wrote: littlesincanada writes: On the face of it, a rebase is the obvious solution, but I'm told that it's a cardinal sin to rebase commits that have already been pushed. So forget about that cardinal sin and just rebase.

Re: Branch management

littlesincanada writes: > Hi Devs, > It's a long time since I pushed any Lilypond dev work to my dev branch > dev/rlittle. About 9 years to be precise. :o > OK, time that situation changed. > > The only commit on that branch is a first pass at a Braille output >

Branch management

Hi Devs, It's a long time since I pushed any Lilypond dev work to my dev branch dev/rlittle. About 9 years to be precise. :o OK, time that situation changed. The only commit on that branch is a first pass at a Braille output option base. Things have moved on and I'm working on it some more,

Re: Doc: CG update Indenting with vim section (issue 302340043 by mark.opu...@googlemail.com)

On 2016/08/06 13:26:43, Carl wrote: Thanks for doing this -- it helps me understand better how things work, and gives an example of a more robust set of vim settings. https://codereview.appspot.com/302340043/diff/1/Documentation/contributor/programming-work.itexi File

Re: Issue 4936: look up "mf" for default initial volume (issue 308890043 by nine.fierce.ball...@gmail.com)

On 2016/08/10 23:05:23, c_sorensen wrote: When writing congregational hymns, dynamics are very seldom included. But I may wish to generate practice midi from my engraving (I regularly do it). It would be nice to be able to define my own default midi volume that would apply. This is a

Re: Issue 4936: look up "mf" for default initial volume (issue 308890043 by nine.fierce.ball...@gmail.com)

On 2016/08/10 23:05:23, c_sorensen wrote: On 8/10/16 4:17 PM, mailto:"nine.fierce.ball...@gmail.com; wrote: >David, do you have advice on the direction to take regarding the >comments on this thing in midi.scm? > > (define-public

Re: Programming Language

Ricardo Wurmus writes: > Hi Conor, > > David Kastrup writes: > >> For extending LilyPond, you need Scheme. Scheme knowledge is only of >> limited marketing value but of course the general kind of solving >> programming tasks from within a fourth generation

Re: Programming Language

Am 10.08.2016 um 19:09 schrieb David Kastrup: > C++ is a good career move, but the C++ in LilyPond's code base is of > rather mixed quality and of rather mixed age: the early parts had to > rely on the features available in early language standards. So C++ > skills acquired while working with

Re: Programming Language

Hi Conor, David Kastrup writes: > For extending LilyPond, you need Scheme. Scheme knowledge is only of > limited marketing value but of course the general kind of solving > programming tasks from within a fourth generation extension language may > still be reasonably relevant.