"Keith OHara" writes:
so it can take *optional* arguments,
>>> I have not yet learned to use David's new facility for optional arguments...
>>
>> Please report the parts of the documentation you find hard to
>> understand. Optional arguments are quite easy to use: if reading the
>> documen
so it can take *optional* arguments,
I have not yet learned to use David's new facility for optional arguments...
Please report the parts of the documentation you find hard to
understand. Optional arguments are quite easy to use: if reading the
documentation gives you a headache, there is som
Hi all,
unfortunately i haven't finished my move yet and i don't even have internet
access in home yet. Therefore, i estimate that i'll come back to Lily work
in the next week.
If there is anything requiring my assistance, write to this address - i'll
try to check it soon.
cheers,
Janek
yes, fine, LGTM, push it.
http://codereview.appspot.com/5155045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I got a little ahead of myself...the patch, while it works in the
regtest cases, does not work the way I think it did because all Items'
pure heights are calculated from 0 to INT_MAX in Separation_item::boxes.
Certain NonMusicalPaperColumns' horizontal skylines will change
depending on if they be
This new patch set eliminates all regtest diffs via a mechanism that
allows extremal lyrics to be flush with the left edge.
It kinda sorta bends LilyPond into doing something it is not designed to
do :: returning pureY-extents for items that are dependent on the start
and end positions (normally,
On 2011/10/10 07:40:24, mike_apollinemike.com wrote:
Yes'r. I think that this will be useful in the same way that
Skyline::print is
useful (I use them in tandem).
This is not meant as a criticism of you in this case, but as a general
observation: we have locked away too many parts of Lilypo
2011/10/10 Federico Bruni :
>>> But it doesn't seem to be the right committish.
>>
>> What exactly did you do to find out this committish? That could be
>> right, it matches a commit by you in which you run makelsr.py, so it
>> shouldn't give any "bad object" messages.
>>
> I checked the log of fil
On Oct 10, 2011, at 9:26 AM, d...@gnu.org wrote:
> On 2011/10/10 07:15:35, MikeSol wrote:
>> The newest patchset adds a debug function to bug.cc.
>
> Not according to the uploaded patch sets.
>
>
Sorry, box.cc I meant.
>> I'd push it as a separate
>> commit - it has helped me a lot with this
On 2011/10/10 07:15:35, MikeSol wrote:
The newest patchset adds a debug function to bug.cc.
Not according to the uploaded patch sets.
I'd push it as a separate
commit - it has helped me a lot with this & other patches & I'd like
to keep it
in the code base.
Just make sure that it can rea
Il 10/10/2011 00:28, Francisco Vila ha scritto:
2011/10/9 Federico Bruni:
I've tried:
cd Documentation/it/texidocs
sed -i
's/514674cb00c18629242dfcde0c1a4976758adc56/34607d3e36a93030690ccd780a7ffce621ca1e0f/g'
*.texidoc
But it doesn't seem to be the right committish.
What exactly did you do t
Hey all,
The newest patchset adds a debug function to bug.cc. I'd push it as a
separate commit - it has helped me a lot with this & other patches & I'd
like to keep it in the code base.
Cheers,
MS
http://codereview.appspot.com/5235052/
___
lilypond-
12 matches
Mail list logo
