Comment #2 on issue 1774 by philehol...@googlemail.com: Semi-breves
unnecessarily shifted
http://code.google.com/p/lilypond/issues/detail?id=1774
I've looked in both Gould and Read, and neither is explicit about placement
with semi-breves. However, both state that simultaneous music
Comment #5 on issue 1604 by philehol...@googlemail.com: MultiMeasureRest
staff position 0 is taken as staff position 2
http://code.google.com/p/lilypond/issues/detail?id=1604
Adding an image.
Attachments:
1604.png 6.3 KB
___
Updates:
Labels: -Patch-new Patch-needs_work
Comment #5 on issue 36 by pkx1...@gmail.com: collision cresc and kneed beams
http://code.google.com/p/lilypond/issues/detail?id=36
Hello, make is fine but when I do a reg test comparions I get an error.
Unfortunately I cannot see exactly
Comment #10 on issue 1663 by bealings...@googlemail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
AFAICS, running make; make doc; make website; doesn't create the HTML
versions of the manuals - not on my system, anyway. Is there a make
command
Comment #11 on issue 1663 by philehol...@googlemail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
Comment 10 was me - other browser, other username.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Comment #5 on issue 1733 by philehol...@googlemail.com: \displayLilyMusic
ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
If I run the command above with 2.15.5, I get the output at the bottom.
I'm not convinced that's correct.
Processing `1733.ly'
Parsing...
Updates:
Status: Verified
Mergedinto:
Comment #3 on issue 868 by philehol...@googlemail.com: \parenthesize does
not take dotted notes into account
http://code.google.com/p/lilypond/issues/detail?id=868
(No comment was entered for this change.)
Updates:
Owner: mts...@gmail.com
Labels: -Patch-new Patch-review
Comment #12 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
make tests pass and reg tests look pretty good (attached
Comment #6 on issue 1733 by d...@gnu.org: \displayLilyMusic ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
I don't see anything wrong with the reaction for this input. The input
itself is nonsensical and should use ##t rather than #t.
So I think the problem is
Updates:
Labels: -Patch-new Patch-review
Comment #10 on issue 1214 by pkx1...@gmail.com: Cue notes to music that
creates a sub-voice does not work
http://code.google.com/p/lilypond/issues/detail?id=1214
make passes and reg test check is ok.
Updates:
Labels: -Patch-new Patch-review
Comment #1 on issue 1777 by pkx1...@gmail.com: adds auto-generated
documentation for context modifications
http://code.google.com/p/lilypond/issues/detail?id=1777
Passes make and reg tests.
James
Issue 153: \once \set fails to restore previous setting
http://code.google.com/p/lilypond/issues/detail?id=153
This issue is now blocking issue 1744.
See http://code.google.com/p/lilypond/issues/detail?id=1744
--
You received this message because you are listed in the owner
or CC fields of this
lilypond-4 wrote:
If I run the command above with 2.15.5, I get the output at the bottom.
I'm not convinced that's correct.
Unbound variable: t
\tweak #'transparent ##unspecified c e
an old question: should it be ##t or just #t?
a small example to illustrate the dilemma (from the
Updates:
Labels: -Patch-new
Blockedon: 153
Comment #5 on issue 1744 by pkx1...@gmail.com: \once \set behavior should
be documented
http://code.google.com/p/lilypond/issues/detail?id=1744
(No comment was entered for this change.)
Updates:
Status: Verified
Comment #7 on issue 1733 by philehol...@googlemail.com: \displayLilyMusic
ignores \tweak
http://code.google.com/p/lilypond/issues/detail?id=1733
(No comment was entered for this change.)
___
bug-lilypond mailing
parser.yy contains the following code:
music_function_identifier_musicless_prefix: MUSIC_FUNCTION {
SCM sig = scm_object_property (yylval.scm, ly_symbol2scm
(music-function-signature));
if (scm_is_pair (sig) to_boolean (scm_memq (ly_music_p_proc,
scm_cdr
m...@apollinemike.com m...@apollinemike.com writes:
Between the two options attached, which one is better? I like the
first...but I'm the contemporary music attaché and know nothing about
how normal music is supposed to look :)
Both of them use:
\relative c' {
\override Slur #'details
Comment #1 on issue 1776 by pkx1...@gmail.com: doc: \compoundMeter isn't
documented
http://code.google.com/p/lilypond/issues/detail?id=1776
can you like to where the doc show this? or is tis just a request for a
snippet change - just so I am clear.
David Kastrup d...@gnu.org wrote in message
news:87tyacx8iu@fencepost.gnu.org...
parser.yy contains the following code:
music_function_identifier_musicless_prefix: MUSIC_FUNCTION {
SCM sig = scm_object_property (yylval.scm, ly_symbol2scm
(music-function-signature));
if (scm_is_pair (sig)
Updates:
Labels: -Patch-needs_work Patch-review
Comment #6 on issue 1768 by pkx1...@gmail.com: Tremoli can collide with
flags in tight spacing situations.
http://code.google.com/p/lilypond/issues/detail?id=1768
Passes make and reg tests show some differences - nothing significant (in
Phil
I don't see a commit that purports to fix this issue,
nor is one referenced in the bug report.
Have I missed it? Are you sure this is verified?
Trevor
- Original Message -
From: lilyp...@googlecode.com
To: bug-lilypond@gnu.org
Sent: Sunday, July 24, 2011 10:51 AM
Subject: Re:
Hello,
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of
m...@apollinemike.com [m...@apollinemike.com]
Sent: 24 July 2011 11:13
To: codesite-nore...@google.com
Cc:
Hello,
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of
lilyp...@googlecode.com [lilyp...@googlecode.com]
Sent: 24 July 2011 11:11
To: bug-lilypond@gnu.org
Subject: Re: Issue
Between the two options attached, which one is better? I like the
first...but I'm the contemporary music attaché and know nothing about
how normal music is supposed to look :)
The first, perhaps with even more slur curvature to make the distance
to the the corner of the tuplet bracket more
From the response so far I would think that the intersection of
people reasonably comfortable messing with the parser and being
inclined to do extensive reviews is close to non-existent, so I
expect that reviewing, testing and committing the stuff will mostly
be my own job, making sure that
Comment #13 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Not a prob, James!
Cheers,
MS
___
bug-lilypond mailing list
bug-lilypond@gnu.org
On 7/24/11 4:12 AM, -Eluze elu...@gmail.com wrote:
If I run the command above with 2.15.5, I get the output at the bottom.
I'm not convinced that's correct.
Unbound variable: t
\tweak #'transparent ##unspecified c e
an old question: should it be ##t or just #t?
a small example
Updates:
Labels: Patch-new
Comment #6 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Patch at http://codereview.appspot.com/4813048.
___
bug-lilypond mailing
Updates:
Labels: Patch-new
Comment #5 on issue 596 by mts...@gmail.com: collision tuplet number and
slur
http://code.google.com/p/lilypond/issues/detail?id=596
This is actually a different issue than 307. The problem here is the
polynomial solver leads to numerical inaccuracies
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:C36718CD16BC473987DF62923E3D84BF@TrevorLaptop...
Phil
I don't see a commit that purports to fix this issue,
nor is one referenced in the bug report.
Have I missed it? Are you sure this is verified?
Trevor
I was simply verifying
Comment #12 on issue 1663 by percival.music.ca: Images missing on web site
http://code.google.com/p/lilypond/issues/detail?id=1663
It's done with make doc. HTML files are in
out-www/offline-root/something/Documentation/index.html
NB: as always, I make no guarantees that our build system can
Updates:
Labels: -Patch-new Patch-needs_work
Comment #7 on issue 307 by pkx1...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
(No comment was entered for this change.)
___
Werner LEMBERG wl at gnu.org writes:
So I'll try in future to only report bugs on the bug list that I
actually want put in the tracker.
I also agree. Such discussions (even if they are only with
yourself) belong to the devel list.
Me too. I still remember the parser from my attempt
Updates:
Status: Duplicate
Comment #4 on issue 868 by tdaniels...@googlemail.com: \parenthesize does
not take dotted notes into account
http://code.google.com/p/lilypond/issues/detail?id=868
Ignore this - just a test
___
bug-lilypond
Updates:
Labels: -Patch-needs_work Patch-review
Comment #7 on issue 1567 by pkx1...@gmail.com: Add documentation for
footnotes
http://code.google.com/p/lilypond/issues/detail?id=1567
Added more to @known to consider the 'chord' example and also an added
cross ref (both ways) to and
Updates:
Status: Started
Owner: pkx1...@gmail.com
Comment #1 on issue 1730 by pkx1...@gmail.com: Documentation for
lilypond-windows.exe and -dgui option
http://code.google.com/p/lilypond/issues/detail?id=1730
(No comment was entered for this change.)
Updates:
Labels: Patch-review
Comment #2 on issue 1730 by pkx1...@gmail.com: Documentation for
lilypond-windows.exe and -dgui option
http://code.google.com/p/lilypond/issues/detail?id=1730
Patch for this and an additional update to Usage based on an undocumented
feature added to
On 23 July 2011 22:27, Neil Puttock n.putt...@gmail.com wrote:
Here's the scheme engraver if you want to try it out. It's obviously
not as sophisticated as Mike's proposed fix, but it does have the
advantage of aligning absolute dynamics properly (assuming there's a
NoteColumn present at the
Oops, sorry for the late answer!
2011/7/18 Mario Moles mario-mo...@libero.it
even if I correct the syntax (without = c, = d, = f) the error remains.
I'm surprised too.
I've discovered that when you use words for alteration (i.e.
,(ly:make-pitch 0 1 FLAT) for des, ,(ly:make-pitch 0 3 SHARP)
Comment #8 on issue 155 by lemniska...@gmail.com: \parenthesize does not
take accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=155
Interesting. I thought that maybe the parentheses ended up in space
because it was aligned to dot instead of notehead, but this is
Comment #25 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
The critical regression thing was a complete brain fart from me and
should be scornfully ignored. I also now agree that the idea of an
\override
Comment #9 on issue 155 by reinhold...@gmail.com: \parenthesize does not
take accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=155
The parentheses are always vertically aligned with the center of the
stencil. The long vertical line of the b moves it up quite a
2011/7/24 Janek Warchoł lemniskata.bernoull...@gmail.com:
Oops, sorry for the late answer!
2011/7/18 Mario Moles mario-mo...@libero.it
even if I correct the syntax (without = c, = d, = f) the error remains.
I'm surprised too.
I've discovered that when you use words for alteration (i.e.
2011/7/25 Neil Puttock n.putt...@gmail.com:
2011/7/24 Janek Warchoł lemniskata.bernoull...@gmail.com:
Oops, sorry for the late answer!
2011/7/18 Mario Moles mario-mo...@libero.it
even if I correct the syntax (without = c, = d, = f) the error
remains.
I'm surprised too.
I've discovered
Janek Warchoł lemniskata.bernoull...@gmail.com writes:
Oops, sorry for the late answer!
2011/7/18 Mario Moles mario-mo...@libero.it
even if I correct the syntax (without = c, = d, = f) the error remains.
I'm surprised too.
I've discovered that when you use words for alteration (i.e.
Comment #26 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/24 n.puttock:
if we must have the option of switching between old new, I
think a parser-clef.scm entry would make more sense.
I'm not
Comment #8 on issue 621 by k-ohara5...@oco.net: Dynamics should avoid
cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621
Patch at http://codereview.appspot.com/4805054/
Regression test suite shows the expected changes: dynamic text
47 matches
Mail list logo
