2010/1/3 John Mandereau :
> Le samedi 26 décembre 2009 à 11:39 +0100, John Mandereau a écrit :
>> Looking at the .i?tely files will basically work as well, except that it
>> will miss any anchors (nodes, sections...) created by lilypond-book;
>> this is not a big deal, though, as the only ones it c
2010/1/3 John Mandereau :
> Le dimanche 03 janvier 2010 à 10:03 +, Graham Percival a écrit :
>> Because I'm a bad person and should be taken to task over it? I
>> always mean to go back and fix it,
>
> I didn't intend to do anything else with the comment I added. There are
> many other issues
Hi John,
The HTML pages for the documentation on kainhofer.com have code that
looks like this:
...
...
...
Was this caused by your refactoring of the texi2html init file? I'm
asking because the above is not valid HTML, and the colorDefault class
is not used in the docs stylesheet, only in
I can't reproduce this, although looking at the code I can't see how
it's working on my computer. I haven't tried a completely rebuild,
though.
Try this patch; if it fixes the problem on your end, then please push.
Cheers,
- Graham
On Mon, Jan 4, 2010 at 8:49 AM, Patrick McCarty wrote:
> Hi J
New linux binaries with this patch are here:
http://lilypond.org/~graham/
If they work for you (I can't remember what arch you have, so I did
them all), could you send that patch for Jan for pushing to GUB?
Cheers,
- Graham
On Sat, Jan 2, 2010 at 9:27 AM, Patrick McCarty wrote:
> Hello,
>
Due to the euro symbol in the website, we now require the femyr10 font
for tex. This isn't part of the normal tex fonts, since the symbol
didn't exist when tex was originally written.
In ubuntu, you can get it from texlive-fonts-recommended or something like that.
AFAIK we don't have an accurat
Tomorrow I'm off for a few days, meeting some relatives and Trevor.
As previously mentioned, I won't stick to my "2 hours a day" rule
while I'm away; it might be more (if I have a boring train journey) or
much less (if the family is interesting, if there's nice scenery,
etc). I'll resume my normal
Hello all,
I plan to work on the emplementation of bends for lilypond. Some preliminary
tests with scheme were successful, so I want to go to the next stage
soon and
create some new engravers. But there are still some unsolved issues.
But first, a brief explanation for all non-guitarists out t
Hi, I'm the current maintainer of lilypond in openSUSE:Contrib and am in the
process of updating to version 2.12.3.I'm currently having a
bit of a problem with the info files and info is an area that is new to me as
far as packaging and creating are concerned.
1) The man page for lilypond-invoke-
Op maandag 04-01-2010 om 15:33 uur [tijdzone +0200], schreef Dave
Plater:
Hi Dave,
Thanks for mailing us about this!
> I'm the current maintainer of lilypond in openSUSE:Contrib and am in the
> process of updating to version 2.12.3.I'm currently having a
> bit of a problem with the info files a
On 1/4/10 5:38 AM, "Marc Hohl" wrote:
> Hello all,
>
> I plan to work on the emplementation of bends for lilypond. Some preliminary
> tests with scheme were successful, so I want to go to the next stage
> soon and
> create some new engravers. But there are still some unsolved issues.
>
> But
On 01/04/2010 05:11 PM, Jan Nieuwenhuizen wrote:
> Op maandag 04-01-2010 om 15:33 uur [tijdzone +0200], schreef Dave
> Plater:
>
> Hi Dave,
>
> Thanks for mailing us about this!
>
>
>> I'm the current maintainer of lilypond in openSUSE:Contrib and am in the
>> process of updating to version 2.1
On Mon, Jan 4, 2010 at 10:38 AM, Marc Hohl wrote:
> I plan to work on the emplementation of bends for lilypond. Some preliminary
> tests with scheme were successful, so I want to go to the next stage soon
> and
> create some new engravers. But there are still some unsolved issues.
>
> But first, a
> Yes, I am top-posting
I notice that issue 786 was just marked as critical. I sent the
following message to -devel four weeks ago but never received a
response. I'd appreciate advice on how to write messages that are more
responder-friendly.
Chris Snyder wrote:
Issue 786, which was caused b
Op maandag 04-01-2010 om 19:09 uur [tijdzone +0200], schreef Dave
Plater:
> On 01/04/2010 05:11 PM, Jan Nieuwenhuizen wrote:
> > Op maandag 04-01-2010 om 15:33 uur [tijdzone +0200], schreef Dave
> > Plater:
Hi Dave,
> > Another /big/ advantage of building the documentation is that you/we
> > can
Op maandag 04-01-2010 om 19:09 uur [tijdzone +0200], schreef Dave
Plater:
Hi Dave,
I see in the osc log (sadly omitted from the spec's change log):
$ osc log | p
GET https://api.opensuse.org/source/openSUSE:Factory:Contrib/lilypond/_history
---
On 01/04/2010 05:11 PM, Jan Nieuwenhuizen wrote:
> Op maandag 04-01-2010 om 15:33 uur [tijdzone +0200], schreef Dave
> Plater:
>
> Hi Dave,
>
> Thanks for mailing us about this!
>
>
>> I'm the current maintainer of lilypond in openSUSE:Contrib and am in the
>> process of updating to version 2.1
Op maandag 04-01-2010 om 21:00 uur [tijdzone +0200], schreef Dave
Plater:
> On 01/04/2010 05:11 PM, Jan Nieuwenhuizen wrote:
> > Op maandag 04-01-2010 om 15:33 uur [tijdzone +0200], schreef Dave
> Disregard what I said about building the documentation although it seems
> to take a long time. The "
Carl Sorensen schrieb:
On 1/4/10 5:38 AM, "Marc Hohl" wrote:
{[..]
so with bends, I have to add the commands to the parser. Is this correct?
Yes, you will need to add something to the parser, I believe. It's because
bends need to be spanners (they connect notes, so they cover mult
On Mon, 2010-01-04 at 12:22 -0500, Chris Snyder wrote:
> > Yes, I am top-posting
>
> I notice that issue 786 was just marked as critical. I sent the
> following message to -devel four weeks ago but never received a
> response. I'd appreciate advice on how to write messages that are more
> respo
I am confused here. Are you trying to implement the symbols that are
on the tab staff, or on the normal notation?
On Mon, Jan 4, 2010 at 5:44 PM, Marc Hohl wrote:
> Oops, I just sent a mail with an attachment that seems to be too big
> for -devel, I don't know where the limits are for the tablat
Le lundi 04 janvier 2010 à 00:49 -0800, Patrick McCarty a écrit :
> ...
> ...
> ...
>
> Was this caused by your refactoring of the texi2html init file?
Certainly, I botched generation of CSS class attribute for both the new
website and manuals when we merged the two init files. All these ki
Carl Sorensen schrieb:
On 1/4/10 12:29 PM, "Marc Hohl" wrote:
Han-Wen Nienhuys schrieb:
On Mon, Jan 4, 2010 at 10:38 AM, Marc Hohl wrote:
[...]
As bends are musically and technically some sort of slurs, I think the
best way to implement them is mainly to copy the slur eng
Am Donnerstag, 31. Dezember 2009 12:26:39 schrieb Reinhold Kainhofer:
> 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 vers
Le lundi 04 janvier 2010 à 21:00 +0200, Dave Plater a écrit :
> Disregard what I said about building the documentation although it seems
> to take a long time. The "make web" target no longer exists, I'm trying
> it out with "make doc", there is a "make WEB_TARGETS=" but I don't think
> thats wh
Hi Mark,
Could you consider adding something like the following to Git pulling
instructions? Maybe this could be under a @knownissues section (or
"Troubleshooting") at the bottom of the the node "Update command".
%
If pull fails because of a message like
@example
error: Your lo
Oops, I just sent a mail with an attachment that seems to be too big
for -devel, I don't know where the limits are for the tablature list.
I'll upload it to my homepage:
http://www.hohlart.de/marc/bendtest.pdf
Marc
___
lilypond-devel mailing list
lil
Le samedi 02 janvier 2010 à 18:56 -0800, Patrick McCarty a écrit :
> I think that using the chapter name instead of "(main)" would be
> perfect. I'll take care of the CSS problem tonight.
Current style of this button you changed is better, but what about using
lily-home-nav-{bg,hover,active}.png
2010/1/4 John Mandereau :
> Le lundi 04 janvier 2010 à 00:49 -0800, Patrick McCarty a écrit :
>> ...
>> ...
>> ...
>>
>> Was this caused by your refactoring of the texi2html init file?
>
> Certainly, I botched generation of CSS class attribute for both the new
> website and manuals when we merg
On Mon, Jan 4, 2010 at 1:18 AM, Graham Percival
wrote:
> New linux binaries with this patch are here:
> http://lilypond.org/~graham/
>
> If they work for you (I can't remember what arch you have, so I did
> them all), could you send that patch for Jan for pushing to GUB?
The linux-64 and linux
Le lundi 04 janvier 2010 à 16:11 +0100, Jan Nieuwenhuizen a écrit :
> Yes, that's related. The openSUSE extended info install check blindly
> gzips everything it finds, including the target of symlinks that do
> not exist.
>
> The symlinks will help emacs find the images, there need be two
>
>
On 01/04/2010 08:59 PM, Jan Nieuwenhuizen wrote:
> Op maandag 04-01-2010 om 19:09 uur [tijdzone +0200], schreef Dave
> Plater:
>
> Hi Dave,
>
> I see in the osc log (sadly omitted from the spec's change log):
>
> $ osc log | p
> GET https://api.opensuse.org/source/openSUSE:Factory:Contrib/lilypond/
On 1/4/10 3:28 PM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> With the architecture above, I don't think you need to specify bend and
>> release bend. All of the bends you show have a note at each end of the bend
>> (either a real note or a grace note).
>>
> Yes, but there are quar
On 1/4/10 12:29 PM, "Marc Hohl" wrote:
> Han-Wen Nienhuys schrieb:
>> On Mon, Jan 4, 2010 at 10:38 AM, Marc Hohl wrote:
>>
>>> [...]
>>>
>>> As bends are musically and technically some sort of slurs, I think the
>>> best way to implement them is mainly to copy the slur engraver code and to
Le lundi 04 janvier 2010 à 15:03 -0800, Patrick McCarty a écrit :
> I just fixed two of the gradient images in master. I didn't notice
> them before because they are not currently used in the CSS. :-)
>
> For the CSS, you'll want to use nav-bg-2.png, nav-hover-2.png, and
> nav-active-2.png on th
2010/1/4 John Mandereau :
> Le samedi 02 janvier 2010 à 18:56 -0800, Patrick McCarty a écrit :
>> I think that using the chapter name instead of "(main)" would be
>> perfect. I'll take care of the CSS problem tonight.
>
> Current style of this button you changed is better, but what about using
> l
2010/1/4 John Mandereau :
> Le lundi 04 janvier 2010 à 14:18 -0800, Patrick McCarty a écrit :
>> 2010/1/4 John Mandereau :
>> > Current style of this button you changed is better, but what about using
>> > lily-home-nav-{bg,hover,active}.png backgrounds in exactly the same
>> > situations as the fi
Le lundi 04 janvier 2010 à 14:18 -0800, Patrick McCarty a écrit :
> 2010/1/4 John Mandereau :
> > Current style of this button you changed is better, but what about using
> > lily-home-nav-{bg,hover,active}.png backgrounds in exactly the same
> > situations as the first navigation bar? If you like
On 01/04/2010 10:08 PM, John Mandereau wrote:
> Le lundi 04 janvier 2010 à 21:00 +0200, Dave Plater a écrit :
>
>> Disregard what I said about building the documentation although it seems
>> to take a long time. The "make web" target no longer exists, I'm trying
>> it out with "make doc", the
John Mandereau wrote:
> Could you consider adding something like the following to
> Git pulling instructions? Maybe this could be under a
> @knownissues section (or "Troubleshooting") at the bottom
> of the the node "Update command".
Sure thing.
By the way, I had less time than expected last w
On Mon, Jan 04, 2010 at 08:58:11PM -0800, Mark Polesky wrote:
> John Mandereau wrote:
> > Could you consider adding something like the following to
> > Git pulling instructions? Maybe this could be under a
> > @knownissues section (or "Troubleshooting") at the bottom
> > of the the node "Update
LGTM if the two nitpicks are adressed.
http://codereview.appspot.com/183097/diff/4/1002
File scripts/convert-ly.py (right):
http://codereview.appspot.com/183097/diff/4/1002#newcode213
scripts/convert-ly.py:213: class InvalidVersion:
this class should be subclassed from a basic Exception class,
42 matches
Mail list logo
