On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
> *** FAILED BUILD ***
>
> nice make doc -j3 CPU_COUNT=3
>
> Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
>
> Current broken commit: 42984d05239a3c3be1ea859ba5214ce140448afc
LGTM, but are you sure that the info on the Windows download page is
good for lilypond-book, as well as for lilypond itself?
http://codereview.appspot.com/5521056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/lis
On 2012/01/09 08:46:36, Graham Percival wrote:
LGTM, but are you sure that the info on the Windows download page is
good for
lilypond-book, as well as for lilypond itself?
on my own windows machine:
--snip--
C:\Program Files\LilyPond\usr\bin>lilypond-book.py --version
2.14.2
C:\Program File
On Mon, Jan 09, 2012 at 08:22:50AM +, Graham Percival wrote:
> On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
> wrote:
> > *** FAILED BUILD ***
> >
> > nice make doc -j3 CPU_COUNT=3
> >
> > Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
>
On Jan 9, 2012, at 10:18 AM, Graham Percival wrote:
> On Mon, Jan 09, 2012 at 08:22:50AM +, Graham Percival wrote:
>> On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
>> wrote:
>>> *** FAILED BUILD ***
>>>
>>> nice make doc -j3 CPU_COUNT=3
>>>
>>> Previous
Hello again,
Am 07.01.2012 09:42, schrieb David Kastrup:
Actually, this is quite too complicated...
(ly:parser-include-string parser
(format #f "\\include ~S" file))
should likely be all that is needed here.
Sorry for thinking too complicated.
so its just:
--snip--
#(define-public includ
2012/1/8 Janek Warchoł :
> ok, i think i understand what you said (that's a success :) ), but i
> don't know what should i use instead of glyph-name callback - a hint
> please?
Write an offset callback instead? It should be safe to access
glyph-name at that point.
Cheers,
Neil
http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1366
Documentation/notation/rhythms.itely:1366: The @code{\partial
@var{du
On 2012/01/09 12:58:58, Neil Puttock wrote:
http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1366
Documentation/notatio
Note that this is misleading:
\relative c' {
\partial 4
c4
\applyContext #(lambda (ctx)
(newline)
(display (ly:context-current-moment ctx)))
c1
}
-> #
The Rational class doesn't display negative rationals unless they're
infinite.
http://coderevi
I totally share your sentiment, but we depend on an external entity
here, which we cannot control. Suppose we go from 2.15.x to 2.17.x and
put the documentation under "v2.17". For some time, Google won't have
the new location in its index, so the search would get nothing. It
would be better to
Janek Warchoł writes:
> According to our motto the aim of LilyPond is "music engraving to
> everyone" - i'd say it's a very good goal. It would mean that a
> person with average computer skills (like navigating a web browser and
> using word processor) should be able to create very good engravin
- Original Message -
From:
To:
Cc: ;
Sent: Monday, January 09, 2012 5:14 AM
Subject: Re: Gets rid of PostScript
inbar-chords-notation-for-guitar--with-text-spanner.ly (issue 5529048)
LGTM
I'm vaguely curious as to what's the difference between this postscript
and the regtest for
- Original Message -
From: "Graham Percival"
To:
Cc:
Sent: Monday, January 09, 2012 8:22 AM
Subject: Re: Patchy email
On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
nice make doc -j3 CPU_COUNT=3
Previous good commit: 820c7ff
- Original Message -
From:
To:
Cc: ;
Sent: Monday, January 09, 2012 9:04 AM
Subject: Re: Doc: Usage - added link for Windows users (issue 5521056)
On 2012/01/09 08:46:36, Graham Percival wrote:
LGTM, but are you sure that the info on the Windows download page is
good for
lilypond-
- Original Message -
From:
To: ;
Cc: ;
Sent: Monday, January 09, 2012 2:10 PM
Subject: Re: Doc search: update to version 2.15, use it in the "site:"
part(issue 5530043)
I totally share your sentiment, but we depend on an external entity
here, which we cannot control. Suppose we g
On Mon, 9 Jan 2012 14:24:45 -, Phil Holmes wrote:
- Original Message - From:
To:
Cc: ;
Sent: Monday, January 09, 2012 5:14 AM
Subject: Re: Gets rid of PostScript
inbar-chords-notation-for-guitar--with-text-spanner.ly (issue
5529048)
LGTM
I'm vaguely curious as to what's the d
- Original Message -
From:
To:
Sent: Monday, January 09, 2012 4:32 PM
Subject: Re: Gets rid of
PostScriptinbar-chords-notation-for-guitar--with-text-spanner.ly (issue
5529048)
On Mon, 9 Jan 2012 14:24:45 -, Phil Holmes wrote:
- Original Message - From:
To:
Cc: ;
Se
- Original Message -
From: "Graham Percival"
To:
Cc:
Sent: Monday, January 09, 2012 8:22 AM
Subject: Re: Patchy email
On Sun, Jan 08, 2012 at 10:37:51PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
nice make doc -j3 CPU_COUNT=3
Previous good commit: 820c7ff
On Sat, 7 Jan 2012 01:54:06 +0100
Janek Warchoł wrote:
> W dniu 7 stycznia 2012 01:40 użytkownik Carl Sorensen
> napisał:
...
> > Are you measuring staff space in pixels from the top of one staff
> > line to the top of the next staff line?
>
> Yes, exactly like that. I was often measuring one
Personally I find the thicker beams look much better.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Does this do anything to the
\auto-footnote
command as well?
http://codereview.appspot.com/5527058/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Looks *very* good to me!
I really like having only one \footnote command; it's intuitive for
users. Thanks for doing this!
http://codereview.appspot.com/5527058/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/li
On 9 January 2012 20:49, wrote:
> Looks *very* good to me!
>
> I really like having only one \footnote command; it's intuitive for
> users. Thanks for doing this!
On the shoulders of Giants eh David ;)
I can help with the doc if you like, perhaps download the diff file
from the tracker, apply
On Sun, Jan 8, 2012 at 3:39 PM, Xavier Scheuer wrote:
> Hi,
>
> I noticed this while replying to James.
>
> \override Hairpin #'minimum-length = #8 does not take into account the
> fact that a hairpin can be shortened by the presence of a DynamicText.
>
> "minimum-length" is applied not the real
On Mon, Jan 09, 2012 at 02:24:45PM -, Phil Holmes wrote:
> It
> actually looks like the only substantive change if with the
> Documentation/snippets/bar-chords-notation-for-guitar--with-text-spanner.ly
> which is duplicated in snippets/new. Mike - you only need to edit
> the one in snippets/n
On Mon, Jan 09, 2012 at 02:10:24PM +, plros...@gmail.com wrote:
> I totally share your sentiment, but we depend on an external entity
> here, which we cannot control. Suppose we go from 2.15.x to 2.17.x and
> put the documentation under "v2.17". For some time, Google won't have
> the new loca
Quoting Graham Percival :
On Mon, Jan 09, 2012 at 02:10:24PM +, plros...@gmail.com wrote:
I totally share your sentiment, but we depend on an external entity
here, which we cannot control. Suppose we go from 2.15.x to 2.17.x and
put the documentation under "v2.17". For some time, Google w
On Tue, Jan 10, 2012 at 12:15:43AM -0500, Pavel Roskin wrote:
> Quoting Graham Percival :
>
> >Great point! Could you add a comment to this effect to the top of
> >this file? there's no way that I'll remember otherwise.
>
> I believe the comment belongs to some other file that describes the
> r
Thanks, David!
http://codereview.appspot.com/5527058/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/5527058/diff/1/python/convertrules.py
File python/convertrules.py (right):
http://codereview.appspot.com/5527058/diff/1/python/convertrules.py#newcode3362
python/convertrules.py:3362:
From an orthogonal point of view, those variables should be either named
`matchstr
LGTM. Good work!
The only think I'd ask is that you change the markup syntax before
pushing the patch. I think that, if the distinction between footnote
and auto-footnote is going to be eliminated, it needs to be categorical.
http://codereview.appspot.com/5527058/
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Czech team of translators. The file is available at:
http://translationproject.org/latest/lilypond/cs.po
(We can arrange things so that
33 matches
Mail list logo
