Janek Warchoł gmail.com> writes:
> The change is almost certainly due to new beam collision algorithm.
> I'm forwarding this message to the development team so that they will
> know about this issue.
> I'm not sure if it's a bug, though
I think it is a documentation issue. Sometimes we need to
Ian,
thanks for review!
http://codereview.appspot.com/4410049/diff/16001/input/regression/shortened-flags-cues.ly
File input/regression/shortened-flags-cues.ly (right):
http://codereview.appspot.com/4410049/diff/16001/input/regression/shortened-flags-cues.ly#newcode6
input/regression/shortened
On 2011/06/09 08:12:53, MikeSol wrote:
Hey Janek,
All the metafont stuff looks good! Last time we touched base, I
recall that we
had talked about looking into embedding a lot of this info into the
font - did
that prove to be not doable? Other than that, I have one comment
below about
t
On 10/06/11 09:30, lemniskata.bernoull...@gmail.com wrote:
> Ian,
>
> thanks for review!
> http://codereview.appspot.com/4410049/diff/16001/lily/stem.cc#newcode792
> lily/stem.cc:792:
> On 2011/06/09 04:55:10, Ian Hulin (gmail) wrote:
>> /*
>> Look up the font character allowing for the varian
2011/6/10 Carl Sorensen :
>
> On 6/9/11 3:18 PM, "Janek Warchoł" wrote:
>
>> I remember that i tried doing this separation, but
>> something didn't work. I hope i have that draft somewhere though.
>
> I think that what causes problems is you lose the definition of
> black-notehead-width (which com
Hello,
LilyPond 2.14 is released, so I reopen this thread.
Could you put this request into your track, please?
I offer 1.35 bitcoins bounty.
Thank you!
Carlo
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listin
- Original Message -
From: "Carlo Stemberger"
To:
Sent: Friday, June 10, 2011 1:49 PM
Subject: Re: [wishlist] enhancing text spanners
Hello,
LilyPond 2.14 is released, so I reopen this thread.
Could you put this request into your track, please?
I can't find a reference to this req
Hi Phil,
Phil Holmes philholmes.net> writes:
> I can't find a reference to this request - could you repost it, please?
This is the thread:
http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/29244/focus=36655
> What's that in Euros?
Currently more or less 25-30 €, but bitcoin raises very
2011/6/6 Graham Percival
>
> On Mon, Jun 06, 2011 at 11:11:00AM +0200, Jan Warchoł wrote:
> > 2011/6/6 Graham Percival
> > >
> > > Proposal: let’s follow PEP-8.
> > > http://www.python.org/dev/peps/pep-0008/
> > >
> > > * use 4 spaces per indentation level
> > > * never max tabs and spaces
On 6/10/11 5:43 AM, "Janek Warchoł"
wrote:
> 2011/6/10 Carl Sorensen :
>>
>> On 6/9/11 3:18 PM, "Janek Warchoł" wrote:
>>
>>> I remember that i tried doing this separation, but
>>> something didn't work. I hope i have that draft somewhere though.
>>
>> I think that what causes problems is
Oops, forgot to cc to the list...
2011/6/10 Janek Warchoł :
> 2011/6/10 Marc Hohl
>>
>> Am 10.06.2011 13:43, schrieb Janek Warchoł:
>>>
>>> [...]
>>> Unfortunately i still don't know how to extract the information about
>>> black_notehead_width. It should be made some kind of a global
>>> variabl
Carl,
2011/6/10 Carl Sorensen :
>
> On 6/10/11 5:43 AM, "Janek Warchoł"
> wrote:
>> Unfortunately i still don't know how to extract the information about
>> black_notehead_width. It should be made some kind of a global
>> variable, but the main problem is that its value is not specified
>> explic
with Carl's help, new patch set was uploaded. Now the flags aren't
squished, so it's perhaps ready to go :)
http://codereview.appspot.com/4273119/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-de
Trevor:
> I've attached an email which explains a similar problem
...
Path-mtu-discovery is described in rfc-1191 and some problems with it
in rfc-2923. The symtoms described in is matches
"black hole" in rfc-2923.
It should be wholly agnostic to the "git fetch --depth 1" vs.
"git clone" choise
On 6/10/11 2:53 PM, "Janek Warchoł"
wrote:
> Carl,
>
> 2011/6/10 Carl Sorensen :
>> It may be as simple as eliminating the save statement for
>> black_notehead_width.
>
> it works! You are a GENIOUS!!
>
I'm sure that genius is too strong a word to apply to me, but thanks for the
kind words.
E
Looks good, but untested. I'll test it when I can.
http://codereview.appspot.com/4273119/diff/3001/mf/feta-noteheads.mf
File mf/feta-noteheads.mf (right):
http://codereview.appspot.com/4273119/diff/3001/mf/feta-noteheads.mf#newcode45
mf/feta-noteheads.mf:45: numeric black_notehead_width;
Perha
On 6/10/11 12:05 AM, "Keith OHara" wrote:
> James Lowe datacore.com> writes:
>>
>> I think we have some duplication in this section but would like a second
>> opinion
>
> I agree. The two snippets do not need to be quoted in the documentation
> because
> you cover all the concepts earlier.
I
2011/6/11 :
Looks good, but untested. I'll test it when I can.
Ok. Don't forget to make clean in build/mf - there are still missing
dependencies.
Thanks!
http://codereview.appspot.com/4273119/diff/3001/mf/feta-noteheads.mf
File mf/feta-noteheads.mf (right):
http://codereview.appspot.com/4
LGTM.
http://codereview.appspot.com/4273119/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
19 matches
Mail list logo
