Yet more architectural changes to GUB, so I thought it'd be worth
hearing if it works. lilypad should be included automatically now.
http://lilypond.org/~graham/
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu
Hi Graham
With Vista Home Premium and 2.13.10-1.mingw.exe:
Downloaded - OK
Installed - OK
Lilypad - 2 issues
I don't run with administrator privileges
so can't save to /Public/Desktop. Saved in
my 'home' folder. Then OK, except that pdf
does not display the url (Never looked for
this befo
Sorry, I'm a bit woozy from being up past my bedtime. Does the below
translate to "no (definitely) new problems" ?
I'm not asking for a pile of release-related bugs here; I just want to
know if the release process has any regressions against previous
versions. I'd kind-of like to get 2.13.10 out
Am Donnerstag, 31. Dezember 2009 11:29:14 schrieb Trevor Daniels:
> convert-ly - OK, except
> Happened to try a file with \version "2.10"
> This causes a python index error.
Ouch, convert-ly assumed that all version strings always consist of three
entries... I've created a patch to really che
Graham, you wrote Thursday, December 31, 2009 10:44 AM
I'm not asking for a pile of release-related bugs here; I just
want to
know if the release process has any regressions against previous
versions.
I just checked all these issues against 2.13.9.
All were faults in 2.13.9 too except for th
Reinhold Kainhofer wrote Thursday, December 31, 2009 11:26 AM
Am Donnerstag, 31. Dezember 2009 11:29:14 schrieb Trevor Daniels:
convert-ly - OK, except
Happened to try a file with \version "2.10"
This causes a python index error.
Ouch, convert-ly assumed that all version strings always
On Tue, 2009-12-29 at 15:48 -0700, Carl Sorensen wrote:
> On 12/29/09 2:14 PM, "Joe Neeman" wrote:
> > I much prefer leaving it as a context property. Grob properties of the
> > TimeSignature grob should be things that affect the appearance of the
> > TimeSignature grob, not the creation of beams.
Carl Sorensen schrieb:
On 12/30/09 7:42 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
On 12/30/09 6:06 AM, "Marc Hohl" wrote:
@Carl:
I am not at all familiar with SVG. Could you please produce a file
similar to the one you sent already with different rotating angles?
On 12/31/09 6:37 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 12/30/09 7:42 AM, "Marc Hohl" wrote:
>>
>>
>>> Carl Sorensen schrieb:
>>>
>>
>> OK, I've attached a 300 dpi png and with the clef rotated from 0 to 4
>> degrees.
>>
> Thanks for your work, Carl.
>> An Inkscap
On 12/31/09 5:18 AM, "Joe Neeman" wrote:
> On Tue, 2009-12-29 at 15:48 -0700, Carl Sorensen wrote:
>> On 12/29/09 2:14 PM, "Joe Neeman" wrote:
>>> I much prefer leaving it as a context property. Grob properties of the
>>> TimeSignature grob should be things that affect the appearance of the
>
Carl Sorensen writes:
> On 12/31/09 5:18 AM, "Joe Neeman" wrote:
>
>> I don't know the reason; I don't think I was even using LilyPond back
>> in the 2.0 days. But it does sound perfectly reasonable to have
>> context (or translation, if you prefer) properties that can be
>> overridden and reve
Carl Sorensen schrieb:
On 12/31/09 6:37 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
On 12/30/09 7:42 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
OK, I've attached a 300 dpi png and with the clef rotated from 0 to 4
degrees.
Thanks for your work
On 12/31/09 7:45 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 12/31/09 6:37 AM, "Marc Hohl" wrote:
>>
>>
>>> Carl Sorensen schrieb:
>>>
On 12/30/09 7:42 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>
>
OK, I've at
On Thu, Dec 31, 2009 at 10:18 AM, Joe Neeman wrote:
>> > If you were to use a context property, why would you need the special
>> > command \overrideTimeSignatureSettings to change it? That is, why
>> > couldn't people just use \set? If it helps, we could extend \set to
>> > allow nested properti
On 12/31/09 12:46 AM, "Graham Percival" wrote:
> We either need one more button for lily-git, or one less.
>
> Taking a completely hypthetical example, suppose a new doc
> contributors writes a nice addition for the docs, but only uses one
> space after a period (the heretic!). I ask for an
On 12/31/09 8:27 AM, "Han-Wen Nienhuys" wrote:
> On Thu, Dec 31, 2009 at 10:18 AM, Joe Neeman wrote:
>
If you were to use a context property, why would you need the special
command \overrideTimeSignatureSettings to change it? That is, why
couldn't people just use \set? If it h
On Thu, Dec 31, 2009 at 1:43 PM, Carl Sorensen wrote:
Why have we decided that context properties can only be \set, and grob
properties can only be \overridden? In version 2.0 we had two kinds of
properties, layout properties and translation properties. I think that
translat
On 12/31/09 8:56 AM, "Han-Wen Nienhuys" wrote:
> On Thu, Dec 31, 2009 at 1:43 PM, Carl Sorensen wrote:
>
> Why have we decided that context properties can only be \set, and grob
> properties can only be \overridden? In version 2.0 we had two kinds of
> properties, layout propert
Han-Wen Nienhuys writes:
> On Thu, Dec 31, 2009 at 10:18 AM, Joe Neeman wrote:
>
>>> > If you were to use a context property, why would you need the
>>> > special command \overrideTimeSignatureSettings to change it? That
>>> > is, why couldn't people just use \set? If it helps, we could
>>> > ex
On Thu, Dec 31, 2009 at 2:33 PM, Carl Sorensen wrote:
>>> That's actually what the current mechanism is. It uses a special music
>>> function, and I can work within the current limitations.
>>>
>>> However, David was objecting to the special case that timeSignatureSettings
>>> would have as a rev
On 12/31/09 12:44 PM, "Han-Wen Nienhuys" wrote:
> On Thu, Dec 31, 2009 at 2:33 PM, Carl Sorensen wrote:
That's actually what the current mechanism is. It uses a special music
function, and I can work within the current limitations.
However, David was objecting to the spe
>> Would it be a good idea to *draw* these angle brackets instead of
>> using glyphs from a font? I'm thinking that there would be fewer
>> problems that way.
>
> Or maybe we could add a set of angle brackets to the Emmentaler
> font, and use those instead?
I can imagine that we want to have angl
> Would it be a good idea to *draw* these angle brackets instead of
> using glyphs from a font?
Yes. The angle brackets in TeX Gyre Schola (which will eventually
become part of the LilyPond distribution and replace the New Century
Schoolbook fonts) are not too nice IMHO.
Werner
_
>> why can I say
>>
>> \new PianoStaff \with {
>> \override StaffGrouper
>> #'between-staff-spacing #'minimum-distance = #20
>> } ...
>>
>> but not
>>
>> \new Staff \with {
>> \override VerticalAxisGroup
>> #'next-staff-spacing #'minimum-distance = #20
>> } ...
>
> Becau
On Thu, Dec 31, 2009 at 7:35 AM, Werner LEMBERG wrote:
>
>> Would it be a good idea to *draw* these angle brackets instead of
>> using glyphs from a font?
>
> Yes. The angle brackets in TeX Gyre Schola (which will eventually
> become part of the LilyPond distribution and replace the New Century
>
The recent problem with end-of-line in mingw is (believed to be)
fixed; please test the new version here:
http://lilypond.org/~graham/
Also, I'm still waiting to hear if it still works on darwin (any
architecture, any OS version; just make sure you can still generate
any output).
Cheers,
- Gr
On Thu, Dec 31, 2009 at 6:18 PM, Graham Percival
wrote:
> The recent problem with end-of-line in mingw is (believed to be)
> fixed; please test the new version here:
> http://lilypond.org/~graham/
>
> Also, I'm still waiting to hear if it still works on darwin (any
> architecture, any OS versio
Thomas Morgan submitted this patch last July as part of his chord-name work.
http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/22784
It got the provisional OK but never got resubmitted as a single patch,
instead of a series of patches.
We're trying to get the chord-name code finished off.
P
On Thu, Dec 31, 2009 at 3:27 PM, Carl Sorensen wrote:
>
> I took an intermediate approach. The extra button isn't "un-commit", it's
> "wrap the current changes into the previous commit". There isn't as much
> flexibility as the "un-commit" button, but it should handle the hypothetical
> situatio
On 12/31/09 8:27 PM, "Graham Percival" wrote:
> On Thu, Dec 31, 2009 at 3:27 PM, Carl Sorensen wrote:
>>
>> I took an intermediate approach. The extra button isn't "un-commit", it's
>> "wrap the current changes into the previous commit". There isn't as much
>> flexibility as the "un-commit
Neil Puttock gmail.com> writes:
>
> 2009/8/10 Thomas Morgan ziiuu.com>:
>
> > I'm not aware of this (though I don't doubt that you're right).
> > Could you give me an example?
>
> See the attached image, which shows the change in output for the
> regression test `chord-names-languages.ly'.
>
31 matches
Mail list logo
