Hey all,
I'm getting:
Unhandled exception.
[TransientError]
from git-cl. Any ideas as to what that's all about?
Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2013/3/21 David Kastrup :
> Janek Warchoł writes:
>
>> Hi,
>>
>> virtually all grob properties are lowercase words separated with
>> dashes. I think we should get rid of exceptions to this rule and make
>> all grob properties lowercase - here's a list of offenders:
>>
>> minimum-[XY]-extent
>> se
Hi,
On Thu, Mar 21, 2013 at 7:19 PM, m...@mikesolomon.org
wrote:
> To prepare for 2.18, I think we can get it out fastish, but we need to more
> or less freeze current master aside from bug fixes and documentation.
> I have a lot of stuff on the countdown or on patch push that I'm not gonna
> pu
Janek Warchoł writes:
> Hi,
>
> virtually all grob properties are lowercase words separated with
> dashes. I think we should get rid of exceptions to this rule and make
> all grob properties lowercase - here's a list of offenders:
>
> minimum-[XY]-extent
> self-alignment-[XY]
> simple-Y
> [XY]-e
Hi,
virtually all grob properties are lowercase words separated with
dashes. I think we should get rid of exceptions to this rule and make
all grob properties lowercase - here's a list of offenders:
minimum-[XY]-extent
self-alignment-[XY]
simple-Y
[XY]-extent
[XY]-offset
X-positions
potential-X-
Am 21.03.2013 19:19, schrieb m...@mikesolomon.org:
Hey all,
To prepare for 2.18, I think we can get it out fastish, but we need
to more or less freeze current master aside from bug fixes and
documentation. I have a lot of stuff on the countdown or on patch
push that I'm notgonna push for a few m
"m...@mikesolomon.org" writes:
> Hey all,
>
> To prepare for 2.18, I think we can get it out fastish, but we need to
> more or less freeze current master aside from bug fixes and
> documentation. I have a lot of stuff on the countdown or on patch
> push that I'm not gonna push for a few months u
Hey all,
To prepare for 2.18, I think we can get it out fastish, but we need to more or
less freeze current master aside from bug fixes and documentation. I have a
lot of stuff on the countdown or on patch push that I'm not gonna push for a
few months until we get 2.18 out (Ferneyhough hairpin
Janek Warchoł writes:
> On Thu, Mar 21, 2013 at 9:14 AM, wrote:
>
>> I don't know the logic of the code and its uses, so this is basically
>> my unqualified gut feeling and nothing else. Flagging and reporting
>> a "problem" without any user-visible consequences does not appear
>> helpful to m
On Thu, Mar 21, 2013 at 9:14 AM, wrote:
> On 2013/03/21 08:04:42, janek wrote:
>
>> So, you think that we shouldn't report any programming error in these
>> alignment funcitons since an empty extent doesn't prevent us from
>> doing our job i.e. aligning)?
>
> Well, with an empty extent it would a
On 2013/03/21 08:04:42, janek wrote:
So, you think that we shouldn't report any programming error in these
alignment
funcitons since an empty extent doesn't prevent us from doing our job
(i.e.
aligning)?
Well, with an empty extent it would appear our job of aligning _self_ is
already done
Thanks for review!
https://codereview.appspot.com/7533046/diff/3001/lily/self-alignment-interface.cc
File lily/self-alignment-interface.cc (right):
https://codereview.appspot.com/7533046/diff/3001/lily/self-alignment-interface.cc#newcode63
lily/self-alignment-interface.cc:63: programming_error
12 matches
Mail list logo
