On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote:
> Thanks Richard, I never used it and I ignored its existence. I'll add
> that directory to the path in .bashrc.
In light of the further steps it isn't useful to add that directory to
the PATH (because the command will not work unless the it
http://www.downforeveryoneorjustme.com/lilypond.org
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 21/09/14 08:55, Richard Shann wrote:
> On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote:
>> Thanks Richard, I never used it and I ignored its existence. I'll add
>> that directory to the path in .bashrc.
> In light of the further steps it isn't useful to add that directory to
> the PATH
On 21/09/14 08:55, Richard Shann wrote:
> On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote:
>> Thanks Richard, I never used it and I ignored its existence. I'll add
>> that directory to the path in .bashrc.
> In light of the further steps it isn't useful to add that directory to
> the PATH
On Sun, 2014-09-21 at 09:14 +0100, James wrote:
> On 21/09/14 08:55, Richard Shann wrote:
> > On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote:
> >> Thanks Richard, I never used it and I ignored its existence. I'll add
> >> that directory to the path in .bashrc.
> > In light of the further
Reviewers: ,
Message:
Hello, if those that have put in these recent features and enhancements
that are listed in this checkin to the 'Changes' list can come up with
some minimal examples to illustrate them I'd be very appreciative.
I don't pretend to understand all the enhancements and if you th
On 21/09/14 10:30, Richard Shann wrote:
> On Sun, 2014-09-21 at 09:14 +0100, James wrote:
>> On 21/09/14 08:55, Richard Shann wrote:
>>> On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote:
Thanks Richard, I never used it and I ignored its existence. I'll add
that directory to the pat
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode69
Documentation/changes.tely:69: \once \override ChorName.text = #"foo"
ChordName.text
Maybe mak
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode127
Documentation/changes.tely:127: the existing @code{\keepWithTag} and
@code{removeWithTag} comm
Just some minor nitpicks, as I cannot speak about the details of the
recent changes.
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode105
Document
Don Armstrong writes:
> What is the current status of #1055[1] (support for Guile 2.0 in
> lilypond)?
I'm currently working on it. There is a branch dev/guilev2 with the
current work. Current objective is to make it through the test suite.
Several crashes so far look like the memory management
2014-09-21 11:30 GMT+02:00 Richard Shann :
> I described the problem as being to do with building docs just because
> of the error message, but I can't reconstruct this (by doing make on the
> master branch) because lilypond.org is down, so I can't get back to the
> web page which details the auto
[1][macupdate-logo.png]
top background
App Listing Updated
Hi lilypond.org, We have updated your application listing for LilyPond
2.19.14-1 on [2]MacUpdate.com. Please take a moment to review your
On Sun, 21 Sep 2014, David Kastrup wrote:
> Don Armstrong writes:
>
> > What is the current status of #1055[1] (support for Guile 2.0 in
> > lilypond)?
>
> I'm currently working on it. There is a branch dev/guilev2 with the
> current work. Current objective is to make it through the test suite.
Don Armstrong writes:
> Could you point me at a list of guile 2.0 bugs which are affecting
> lilypond? Having that list handy would help me convince the guile
> maintainer (and also Debian's release managers and security) that
> there were valid reasons to keep guile 1.8 for another release of
>
On Sun, 21 Sep 2014, Don Armstrong wrote:
> OK. I *might* be able to convince the guile maintainer to keep 1.8 just
> for lilypond, but that also might mean that I'll end up having to
> maintain guile 1.8 too.
>
> Could you point me at a list of guile 2.0 bugs which are affecting
> lilypond? Havin
On Sun, 21 Sep 2014, David Kastrup wrote:
> Don Armstrong writes:
>
> > Could you point me at a list of guile 2.0 bugs which are affecting
> > lilypond? Having that list handy would help me convince the guile
> > maintainer (and also Debian's release managers and security) that
> > there were val
On Sun, 21 Sep 2014, David Kastrup wrote:
> Don Armstrong writes:
>
> > Could you point me at a list of guile 2.0 bugs which are affecting
> > lilypond? Having that list handy would help me convince the guile
> > maintainer (and also Debian's release managers and security) that
> > there were val
David Kastrup writes:
> It's not clear how long I'll take to wear down the bugs. Half of them
> are other things that go "ugh", like GUILE being of the opinion it knows
> how to deal with various character encodings, reinterpreting strings as
> byte streams and vice versa in situations where it
Don Armstrong writes:
> On Sun, 21 Sep 2014, David Kastrup wrote:
>> Don Armstrong writes:
>>
>> > Could you point me at a list of guile 2.0 bugs which are affecting
>> > lilypond? Having that list handy would help me convince the guile
>> > maintainer (and also Debian's release managers and se
David Kastrup writes:
> GUILE-1.8 already aborts at the attempt of converting 2000 to a
> character. That's a clearcut limitation with understandable effects.
> But whatever you manage to turn into a character will then pass through
> strings or with-in/output-from/to-string or whatever else unm
Thanks to those that checked. New patch uploaded
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode69
Documentation/changes.tely:69: \once \overrid
On Sun, 21 Sep 2014, David Kastrup wrote:
> Don Armstrong writes:
> > I'm just trying to keep lilypond in Debian.
>
> Yes, that would be very desirable.
So it looks like the guile maintainer is going to be willing to ship
guile 1.8 if lilypond doesn't support guile 2.0. So keep up the good
work,
2014-09-21 9:55 GMT+02:00 Richard Shann :
> On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote:
> > Thanks Richard, I never used it and I ignored its existence. I'll add
> > that directory to the path in .bashrc.
> In light of the further steps it isn't useful to add that directory to
> the P
Don Armstrong writes:
> On Sun, 21 Sep 2014, David Kastrup wrote:
>> Don Armstrong writes:
>> > I'm just trying to keep lilypond in Debian.
>>
>> Yes, that would be very desirable.
>
> So it looks like the guile maintainer is going to be willing to ship
> guile 1.8 if lilypond doesn't support g
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode106
Documentation/changes.tely:106: grob can now be aligned on the
@q{center} of its parent.
On 20
26 matches
Mail list logo
