Hi
I'm wanting to write some globally accessible scheme functions / procedures
(defines) for my lilypond project but the documentation on such seems a bit
limited. I.e. Do \header, \page and other contexts introduce new variable
scopes (assuming yes here)? If so, how can scheme functions and va
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'lilypond' has been made available
to the language teams for translation. It is archived as:
http://translationproject.org/POT-files
On Thu, Feb 10, 2011 at 10:57:36PM -0700, Colin Campbell wrote:
> On 11-02-10 10:47 PM, James Lowe wrote:
> >You need to run
> > ../configure
> >again, due to build system changes for new languages. It's /just/
> >possible that you might need to delete your build/ dir and start
> >again, but run
On 11-02-10 10:47 PM, James Lowe wrote:
Hello
From: Graham Percival [gra...@percival-music.ca]
Sent: 10 February 2011 19:47
To: James Lowe
Cc: lilypond-devel@gnu.org
Subject: Re: compiling error with 'unknown' directory 'cs'
On Thu, Feb 10, 2011 at 02:36:
Hello
From: Graham Percival [gra...@percival-music.ca]
Sent: 10 February 2011 19:47
To: James Lowe
Cc: lilypond-devel@gnu.org
Subject: Re: compiling error with 'unknown' directory 'cs'
On Thu, Feb 10, 2011 at 02:36:58PM +, James Lowe wrote:
> I've just
Thanks! Regtests look fine, and there's nothing obviously wrong with
the code.
However, none of the scm files managed to get uploaded. I remember
hearing about problems about this, and the CG now contains:
-
Note: Some installations of git-cl fail when uploading a patch set that
includes a
On Thu, Feb 10, 2011 at 10:06:55PM +0100, Benkő Pál wrote:
> > Add Modal transformations
> > http://codereview.appspot.com/4126042/
>
> I think
> http://codereview.appspot.com/4079064/
> is newer.
Thanks, I have updated the issue in the google tracker.
Cheers,
- Graham
Uploaded. Please check if it is all right now.
2011/2/10 Felipe Gonçalves Assis :
> Hi,
>
> In fact, yesterday's "make key cancellations independent of extraNatural"
> introduced a simple conflict with my patch, which I have just resolved.
>
> Other files were automatically merged.
>
> After some
> Add Modal transformations
> http://codereview.appspot.com/4126042/
I think
http://codereview.appspot.com/4079064/
is newer.
p
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Wow, nice !
Thanks a lot, this really helps :-p
"LaTeX-like" text footnotes are nearly done.
After doing these footnotes and endnotes, I will probably try to implement
drop caps support.
(My secret wish is to get rid of lilypond-book...)
Regards,
Bertrand
__
These are the last two "overdue" patches to review, so the frantic
pace of reviewing will tail off in the next week. I'm hoping to
settle down on 2 patches, twice a week, with 72 hours for each
announcement.
6pm, Saturday 12 Feb, 2011.
Add Modal transformations
http://codereview.appspot.com/412
No complaints, and I just double-checked that the regtest is ok. Please
push.
http://codereview.appspot.com/212048/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, Feb 10, 2011 at 02:36:58PM +, James Lowe wrote:
> I've just done a git pull from this morning and tried to do a 'make ; make
> doc' and get an error
You need to run
../configure
again, due to build system changes for new languages. It's /just/
possible that you might need to delete
Hello,
I've just done a git pull from this morning and tried to do a 'make ; make doc'
and get an error
--
make: Entering an unknown directory
make: *** cs: No such file or directory. Stop.
make: Leaving an unknown directory
make[2]: *** [WWW-1] Error 2
rm out-www/weblinks.itexi
--
I am usin
Hi,
In fact, yesterday's "make key cancellations independent of extraNatural"
introduced a simple conflict with my patch, which I have just resolved.
Other files were automatically merged.
After some testing, I will upload a new patch-set.
Regards,
Felipe
On 10 February 2011 16:13, wrote:
>
Werner LEMBERG writes:
> [Resending to lilypond-devel since it doesn't appear to have reached
> the list (it's missing in
> http://lists.gnu.org/archive/html/lilypond-devel/2011-02/)]
>
>> I tried this patch on half a dozen piano and orchestral scores and
>> saw no bad side-effects.
>
> The att
[Resending to lilypond-devel since it doesn't appear to have reached
the list (it's missing in
http://lists.gnu.org/archive/html/lilypond-devel/2011-02/)]
> I tried this patch on half a dozen piano and orchestral scores and
> saw no bad side-effects.
The attached image (from
IMSLP00014-Beethove
Sorry, I still can't apply this cleanly to git master. Are you sure you
did a rebase? (I admit that I'm not totally certain about how to do
this, but I've seen people in lilypond-devel talking about it -- maybe
look through the mailing list archives for tips?)
At the moment, I see failures in
> I tried this patch on half a dozen piano and orchestral scores and
> saw no bad side-effects.
The attached image (from
IMSLP00014-Beethoven__L.v._-_Piano_Sonata_14.pdf) shows another
solution $(Q#|(B smaller beams $(Q#|(B to avoid the crossing of beams and
stems.
Maybe this can be implemen
Translation: there are some broken links on the website on the german version.
and kudos to the doc editors,
"Hartelijk dank voor de ontwikkeling van Lilypond! Anders als veel
andere notatieprogrammas voelt het aan als een "labor of love". Zelfs
de dokumentatie is een plezier om te lezen. Vooral
LGTM.
http://codereview.appspot.com/4129043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
2011/2/9 Xavier Scheuer :
> %% Reported by 胡海鹏 - Hu Haipeng
> %% http://lists.gnu.org/archive/html/lilypond-user/2011-02/msg00179.html
> %%
> %% [empty] Dynamics context prevents \RemoveEmptyStaves to work
> %%
> %% We should have a way to remove empty Dynamics contexts as well
> %% and \RemoveEmpt
2011/2/10 Phil Holmes :
> Thanks. Now doing a search to try another check to see if there are any
> other references I could have missed.
>
> Where is the location/file that gives the error, please?
I read it on the daily 404 report from lilypond-cvs announce-only list
(sorry, it is not archived)
- Original Message -
From: "Francisco Vila"
To: "Phil Holmes"
Cc: "LilyPond-Devel list"
Sent: Thursday, February 10, 2011 10:47 AM
Subject: 404 for renamed css stylesheets
Hello,
Still some references left to the old lilypond-mccarty.css file:
python/auxiliar/postprocess_html.py
Hello,
to work with foot- or end-notes its good to know the current position in
music - of course this doesn't make sense for a paragraph of pure text ;-)
So I digged for a way to fetch the current position in music - these are
only some hints for me to remember and perhaps for you to try:
--s
On Feb 10, 2011, at 7:50 AM, Han-Wen Nienhuys wrote:
> On Thu, Feb 10, 2011 at 9:54 AM, m...@apollinemike.com
> wrote:
>
>> I think that the problem with doing the collision avoidance in the quanting
>> reveals itself around line 341 of beam-quanting.cc
>> if (collisions_.size ())
>> regio
On Thu, Feb 10, 2011 at 9:54 AM, m...@apollinemike.com
wrote:
> I think that the problem with doing the collision avoidance in the quanting
> reveals itself around line 341 of beam-quanting.cc
> if (collisions_.size ())
> region_size += 2;
> Here, I get the sense that you are expanding the
> The problem is that this requires another layer of code. The
> collision code works for beams individually. For this to be
> resolved like this, there needs to be coordination between the two
> beams. This is much harder, because many such collisions may be
> chained together, eg.
>
> <<
>
2011/2/10 Werner LEMBERG :
>
>> I tried this patch on half a dozen piano and orchestral scores and
>> saw no bad side-effects.
>
> The attached image (from
> IMSLP00014-Beethoven__L.v._-_Piano_Sonata_14.pdf) shows another
> solution �#| smaller beams �#| to avoid the crossing of beams and stems.
>
Hello,
Still some references left to the old lilypond-mccarty.css file:
python/auxiliar/postprocess_html.py , line 154
which cause not_found errors in our website.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypon
"m...@apollinemike.com" writes:
> I like the tunable idea.
>
> Perhaps a grob property named `avoids' that is a list of pairs, kinda like:
>
> '((bar-line . #t) (time-signature . #f) (note-head . #t)) etc...
>
> Then, we could use has_interface to weed out grobs for which we don't
> want to colli
31 matches
Mail list logo
