On 2012/09/22 04:37:42, dak wrote:
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):
Looks OK to me
http://codereview.appspot.com/6532055/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
James pkx1...@gmail.com writes:
I've been looking at the LSR and wondered if this now makes some of
the snippets redundant (or less useful - i.e no need to set a
scheme-type function explicitly).
I.e
http://lsr.dsi.unimi.it/LSR/Item?id=605
qBeam = {
\set beamExceptions =
LGTM - looking forward to the skyline version, as that'll more
accurately reflect where columns are overhanging.
http://codereview.appspot.com/6489107/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Reviewers: Keith,
Message:
I'm gonna hold off on posting to this one as it evolves constantly with
my work on issue 2801, which is revealing several issues in cross-staff
stem calculations. Irrespective of how issue 2801 pans out, I'll take
all the relevant code from stem.cc and either push it
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Saturday, September 22, 2012 5:18 AM
Subject: Re: Apparently the amd64 build of LilyPond 2.16.0 failed on Ubuntu
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David
Phil Holmes m...@philholmes.net writes:
Cf. URL:https://launchpad.net/~dns/+archive/test/+build/3803769
Possibly related to
http://code.google.com/p/lilypond/issues/detail?id=2742 ?
Unlikely that something committed to 2.17.2 is going to affect 2.16.
--
David Kastrup
Am 21.09.2012 11:00, schrieb David Kastrup:
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
I'm trying to build 2.17.3. I get this failure:
make[1]: Entering directory
`/home/gub/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily'
bison -o out/parser-tmp.cc -d
LGTM
http://codereview.appspot.com/6542057/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Phil Holmes em...@philholmes.net writes:
I'm trying to build 2.17.3. I get this failure:
make[1]: Entering directory
/home/gub/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily'
bison -o out/parser-tmp.cc -d
Dear Lilypond developers.
As a mathematician and a casual user of Lilypond, I would like to
share the news about the Bridges conference on math and art, which is
taking place in Entschede, Netherlands, next summer.
http://bridgesmathart.org/bridges-2013/
Since Lilypond was actually started in
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes em...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Saturday, September 22, 2012 4:56 PM
Subject: Re: GUB failure in parser.yy
Phil Holmes em...@philholmes.net writes:
I'm trying to build 2.17.3. I get
On Sat, 22 Sep 2012 01:34:57 -0700, mts...@gmail.com wrote:
LGTM - looking forward to the skyline version, as that'll more
accurately reflect where columns are overhanging.
Well, long term I would like to use extent() to determine which columns have
overlapping extents, but need to find and
Phil Holmes m...@philholmes.net writes:
My preference _right now_ would be to remove the code that's causing
the old version of Bison a problem. To fix Gub, rebuild Gub and then
rebuild lilypond would take considerable time which I don't have now.
I'd like to get an updated version of
Hi,
i'm sorry for the delay :-( There are so many emails flying around
that i find it hard to keep up.
Don't feel obliged to reply to any i don't understand part - i have
so many emails to write that some of my questions may remain
unanswered.
On Sun, Sep 16, 2012 at 6:02 PM, David Kastrup
On Sun, Sep 16, 2012 at 6:05 PM, David Kastrup d...@gnu.org wrote:
Janek Warchoł janek.lilyp...@gmail.com writes:
Hmm, this sounds complicated. Do you mean that implementing more
informative (custom) error messages with current parser will wreak
havoc, but if we simplify the parser first, it
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Saturday, September 22, 2012 6:38 PM
Subject: Re: GUB failure in parser.yy
Phil Holmes m...@philholmes.net writes:
My preference _right now_ would be to
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Saturday, September 22, 2012 6:38 PM
Subject: Re: GUB failure in parser.yy
Phil Holmes m...@philholmes.net
On Thu, Sep 20, 2012 at 11:56 AM, David Kastrup d...@gnu.org wrote:
David Kastrup d...@gnu.org writes:
Within your own scores, be consistent in your choices. How this
consistency looks, does not matter. Within LilyPond, there is a large
consistency which elements are uppercase, and which
On Sat, Sep 22, 2012 at 1:42 PM, Marc Hohl m...@hohlart.de wrote:
It would be interesting to post such issues on the -user list,
because this would give users a possiblility to contribute *and*
to describe the new feature from a user's point of view which
is not a bad thing, after all.
+1.
On Fri, Sep 14, 2012 at 12:00:49AM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
How about considering how they are supposed to translate to and from
Scheme?
Woah. Is the syntax supposed to support translating from scheme
to .ly ?!
Reality check.
On Sat, Sep 22, 2012 at 3:07 PM, Graham Percival
gra...@percival-music.ca wrote:
I have no problem with splitting \tempo into a \tempo_bpm and
\tempoMark command. Or perhaps it would be better to just use
\mark, and add markup functions which mimic the text parts of
the existing \tempo
On Thu, Sep 20, 2012 at 09:05:51PM +, thomasmorle...@googlemail.com wrote:
On 2012/09/20 18:08:15, Graham Percival wrote:
We normally do not include \override in most sections of the Notation
manual.
Instead, we ask users to submit LSR snippets showing the \override,
then we
include
On Sat, Sep 15, 2012 at 10:25:17PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
For example, what about my hated idea of splitting namespaces of
music fuctions and identifiers? I'm not fond of perl, but
something like this is unambiguous:
$F =
On Sat, Sep 22, 2012 at 07:32:20AM +, d...@gnu.org wrote:
Nobody can be bothered enough to even comment.
Yes, that is a problem. I wish that more developers looked at the
countdown and did reviews. For example, many of Keith's changes
in the past month have had absolutely no reviews.
If
On Sat, Sep 22, 2012 at 12:40:13AM +0200, Francisco Vila wrote:
\repeat volta repeatcount { musicexpr
\alternative {
{ musicexpr }
{ musicexpr }
{ musicexpr }
}
}
I do not see a problem here from the user's POV.
Agreed; I quite like this form.
- Graham
Jay Anderson horndud...@gmail.com writes:
On Sat, Sep 22, 2012 at 3:07 PM, Graham Percival
gra...@percival-music.ca wrote:
I have no problem with splitting \tempo into a \tempo_bpm and
\tempoMark command. Or perhaps it would be better to just use
\mark, and add markup functions which mimic
28 matches
Mail list logo
