Am 21.09.2012 00:31, schrieb Thomas Morley:
[...]
Hi David, Marc,
speaking only for me: I'm terrible sorry that I currently can't give
you the feedback you desire. Since my injury, I wasn't able to
concentrate on any more involved project or to finish any larger one.
Also, I let Marc
Marc Hohl m...@hohlart.de writes:
But I don't want to tackle around with the documentation *yet* while
it is not sure that my patch gets accepted and the new interface is
considered a good idea by most of the developers. So while in an
ideal world every programmer enhances the documentation
Hello,
I've been having intermittent Broadband disconnects since late evening
and they were running into this morning.
So if it appears that staging is not getting merged, don't panic it
will eventually - I set Patchy on a 4 hour cycle this morning before I
left for work.
James
Hi,
here's something that i find very inconvenient to express in Lily
syntax. I'm not sure about proper name for this, so just look at the
attachment.
As far as i know, to achieve this notation with LilyPond, i have to write this:
\new Staff
\mergeDifferentlyDottedOn
\new Voice {
On Fri, Sep 21, 2012 at 2:02 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
What's your opinion? How would you do this? Maybe there's no need
for new syntax constructs?
To be more credible, here is my try at doing this with a music function:
sust =
#(define-music-function (parser location
Janek Warchoł janek.lilyp...@gmail.com writes:
On Fri, Sep 21, 2012 at 2:02 PM, Janek Warchoł
janek.lilyp...@gmail.com wrote:
What's your opinion? How would you do this? Maybe there's no need
for new syntax constructs?
To be more credible, here is my try at doing this with a music
Well, the host of different syntaxes to \tempo aside, here are some
other nuisances:
Sometimes it is important to be able to parse some expression without
further lookahead, for example because lexer modes need switching. I am
just now experimenting with code where the _lexer_ will
Cf. URL:https://launchpad.net/~dns/+archive/test/+build/3803769
Anybody have an idea from looking at the build log?
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 21 September 2012 17:46, David Kastrup d...@gnu.org wrote:
Another parser baddy is \alternatives since it means that no \repeat
expression can be considered complete without checking for potentially
following alternatives. It would make more sense if the alternatives
were written
Hello,
On 21 September 2012 18:34, David Kastrup d...@gnu.org wrote:
Cf. URL:https://launchpad.net/~dns/+archive/test/+build/3803769
Anybody have an idea from looking at the build log?
/build/buildd/lilypond-2.16.0/out/lybook-db/snippet-names--4642696709202227756.log
This is the log file to
[oops, +lily-devel]
On Fri, Sep 21, 2012 at 11:00 AM, Joe Neeman joenee...@gmail.com wrote:
On Fri, Sep 21, 2012 at 10:34 AM, David Kastrup d...@gnu.org wrote:
Cf. URL:https://launchpad.net/~dns/+archive/test/+build/3803769
Anybody have an idea from looking at the build log?
A crash
Hello,
On 21 September 2012 19:01, Joe Neeman joenee...@gmail.com wrote:
[oops, +lily-devel]
On Fri, Sep 21, 2012 at 11:00 AM, Joe Neeman joenee...@gmail.com wrote:
On Fri, Sep 21, 2012 at 10:34 AM, David Kastrup d...@gnu.org wrote:
Cf.
James pkx1...@gmail.com writes:
Hello,
On 21 September 2012 19:01, Joe Neeman joenee...@gmail.com wrote:
[oops, +lily-devel]
On Fri, Sep 21, 2012 at 11:00 AM, Joe Neeman joenee...@gmail.com wrote:
On Fri, Sep 21, 2012 at 10:34 AM, David Kastrup d...@gnu.org wrote:
Cf.
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Friday, September 21, 2012 6:34 PM
Subject: Apparently the amd64 build of LilyPond 2.16.0 failed on Ubuntu
Cf. URL:https://launchpad.net/~dns/+archive/test/+build/3803769
Anybody have an idea from
David Kastrup wrote Friday, September 21, 2012 5:46 PM
Well, the host of different syntaxes to \tempo aside, here are some
other nuisances:
[snip]
Look and behold: after the closing brace of the sequential music, the
expression is not finished because LilyPond has to see whether there is
an
2012/9/21 David Kastrup d...@gnu.org:
So \addlyrics is on my blacklist of unnecessarily surprising constructs.
It is massively used (I assume; I have no figures) but it is short,
intuitive and easy to remember.
Then strings in lyrics are sufficiently differently delimited from the
way strings
2012/9/21 James pkx1...@gmail.com:
The NR says at the moment that the construct is
\repeat volta repeatcount musicexpr
\alternative {
{ musicexpr }
insert more optional { musicexpr }... here.
Maybe there are problems when you have
\repeat volta repeatcount { musicexpr
\alternative {
Hi David, James all,
On Fri, Sep 21, 2012 at 7:41 PM, James pkx1...@gmail.com wrote:
About the only part of the thread I could follow [...]
Indeed, David's message was really technical.
I'll try to translate his email. Apart from checking whether i
understood everything correctly myself, i
I only get upload in process, so I've added .pl files to git-cl
exceptions. That said, I think this can be pushed directly.
http://codereview.appspot.com/6540043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
LGTM
http://codereview.appspot.com/6526045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/6532055/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/6532055/diff/1/Documentation/notation/rhythms.itely#newcode1067
Documentation/notation/rhythms.itely:1067: \time #'(2 2 3) 7/8
Janek Warchoł janek.lilyp...@gmail.com writes:
Hi David, James all,
On Fri, Sep 21, 2012 at 7:41 PM, James pkx1...@gmail.com wrote:
About the only part of the thread I could follow [...]
Indeed, David's message was really technical.
I'll try to translate his email. Apart from checking
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Friday, September 21, 2012 6:34 PM
Subject: Apparently the amd64 build of LilyPond 2.16.0 failed on Ubuntu
Cf.
On 2012/09/22 01:30:50, Graham Percival wrote:
LGTM
http://codereview.appspot.com/6532055/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/6532055/diff/1/Documentation/notation/rhythms.itely#newcode1067
LGTM of course
http://codereview.appspot.com/6543046/diff/1/lily/stem.cc
File lily/stem.cc (right):
http://codereview.appspot.com/6543046/diff/1/lily/stem.cc#newcode342
lily/stem.cc:342: // find the offset of various staves as well as the
minimum and maximum offset
How does this find the
25 matches
Mail list logo
