lilyp...@googlecode.com writes:
\RemoveEmptyStaves is defined inside engraver-init.ly, which renders
it inaccessible as an identifier outside a \layout block.
The following snippet causes the parser to emit two errors, and the
second bar isn't removed:
\version 2.15.5
\new Staff
Later in the mentioned chapter of the documentation is shown that
\set melismaBusyProperties = #'()
will probably achieve what you intend.
HTH
Urs
Am 12.07.2011 23:20, schrieb Neil Puttock:
On 12 July 2011 21:08, BognárBálintbobq...@inf.elte.hu wrote:
When autoBeam is off and I manually
Am 12.07.2011 19:13, schrieb Derek Klinge:
These all appear to be the same issue to me. Is it possible to merge some of
the examples from the third issue into the first? I feel like the
tiny.examples in that one most clearly demonstrate the problem.
Derek
I don't know about the internals how
2011/7/13 m...@apollinemike.com m...@apollinemike.com
On Jul 13, 2011, at 1:48 PM, Janek Warchoł wrote:
Is it possible to change gap between beams (i.e. the distance between the
lines) painlessly?
\override Beam #'gap = #2 doesn't work, i don't find anything in LSR nor
Internals...
Comment #17 on issue 1752 by hanw...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Hi guys,
as the original designer of the G-clef, I applaud Janek's work, and don't
see any reason why we can or should not improve the shape of the
Comment #18 on issue 1752 by pkx1...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
'improve'? I don't think it is an improvement at all. It's worse.
Does mine (and the other's who also preferred the original) opinion not
count?
If
Comment #17 on issue 1752 by hanw...@gmail.com: redesigning G clef
in our Feta font
I vote against overrides; we have too many of them, and the
difference between the old and new glyph doesnt warrrant another
option.
I agree. LilyPond has many glyphs. If we start using
overrides to
Comment #4 on issue 1494 by hanw...@gmail.com: including alternate fonts
http://code.google.com/p/lilypond/issues/detail?id=1494
Also, the original site https://sites.google.com/site/jpgzic/home doesnt
have fontforge sources for the font. Can we have confirmation that this is
original work?
On Wed, Jul 13, 2011 at 05:17:11PM +0100, Trevor Daniels wrote:
I vote against overrides; we have too many of them, and the
difference between the old and new glyph doesnt warrrant another
option.
I agree. LilyPond has many glyphs. If we start using
overrides to select glyphs with
On 7/13/11 6:48 AM, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
2011/7/13 m...@apollinemike.com m...@apollinemike.com
On Jul 13, 2011, at 1:48 PM, Janek Warchoł wrote:
Is it possible to change gap between beams (i.e. the distance between the
lines) painlessly?
\override Beam
Comment #3 on issue 1759 by carl.d.s...@gmail.com: hairpin aligns to lyrics
instead of notes
http://code.google.com/p/lilypond/issues/detail?id=1759
I believe this is because the lyrics are at the same moment as the notes,
and the lyrics define the leftmost and rightmost edges of of the
Comment #1 on issue 1755 by bordage@gmail.com: Add Baroque ornaments
http://code.google.com/p/lilypond/issues/detail?id=1755
Several other ornaments could also be added.
9 and 10 in the following image are commonly found in Bach's music:
Am Mittwoch, 13. Juli 2011, 10:56:23 schrieb David Kastrup:
lilyp...@googlecode.com writes:
\RemoveEmptyStaves is defined inside engraver-init.ly, which renders
it inaccessible as an identifier outside a \layout block.
The following snippet causes the parser to emit two errors, and the
Updates:
Labels: -backport fixed_2_14_2
Comment #3 on issue 750 by carl.d.s...@gmail.com: Misleading warning when a
Lyrics context is empty
http://code.google.com/p/lilypond/issues/detail?id=750
Backported
commits a56bb3d5dc80cad99bd8656ec63edd52ca5b59e2
and
Updates:
Labels: -backport fixed_2_14_2
Comment #5 on issue 770 by carl.d.s...@gmail.com: Lyrics behave differently
when associated to a Voice-derived context
http://code.google.com/p/lilypond/issues/detail?id=770
Backported
Commits ceec117d8193985d2d1ad9377d9b467ae31fbf03
and
Updates:
Labels: -Patch-review -backport fixed_2_14_2
Comment #19 on issue 75 by carl.d.s...@gmail.com: Slurs cannot be nested
(including acciaccatura and appoggiatura)
http://code.google.com/p/lilypond/issues/detail?id=75
backported
commits 5c7a95d829b0156bec60cc9e9bd91c52828255cb
Comment #20 on issue 75 by carl.d.s...@gmail.com: Slurs cannot be nested
(including acciaccatura and appoggiatura)
http://code.google.com/p/lilypond/issues/detail?id=75
Scratch those commits. In order to make every commit build the baseline,
I've done a rebase that includes both commits.
Comment #4 on issue 1256 by carl.d.s...@gmail.com: Extra SlurEvent modifies
extents of broken slurs
http://code.google.com/p/lilypond/issues/detail?id=1256
Scratch those commits. In order to make every commit build the baseline,
I've done a rebase that includes both commits.
New commit
Comment #2 on issue 1755 by carl.d.s...@gmail.com: Add Baroque ornaments
http://code.google.com/p/lilypond/issues/detail?id=1755
Nicolas also indicated that a new engraver for side ornaments might be
useful; he has already created such an engraver in Scheme.
Updates:
Labels: -Patch-review -backport fixed_2_14_2
Comment #6 on issue 1581 by carl.d.s...@gmail.com: Pitched trill between
tied notes causes `unterminated tie' warning
http://code.google.com/p/lilypond/issues/detail?id=1581
Backported.
Commit
Updates:
Labels: -Patch-review -backport fixed_2_14_2
Comment #4 on issue 1676 by carl.d.s...@gmail.com: Tremolo with change
staff produces false dotted note
http://code.google.com/p/lilypond/issues/detail?id=1676
Backported.
Commit 5878256d62b303a9a59ccd162dfbfc91524c4cf2
Updates:
Labels: -Patch-review -backport fixed_2_14_2
Comment #3 on issue 1256 by carl.d.s...@gmail.com: Extra SlurEvent modifies
extents of broken slurs
http://code.google.com/p/lilypond/issues/detail?id=1256
backported -- same patch as fix for issue 75
commits
Updates:
Labels: -backport fixed_2_14_2
Comment #7 on issue 1715 by carl.d.s...@gmail.com: Ligature and ambitus
cause segfault
http://code.google.com/p/lilypond/issues/detail?id=1715
Backported (including updates to regtest in
c44c6048c3075c8a4fe5202777f048c6d66d5202 and
Comment #8 on issue 1715 by carl.d.s...@gmail.com: Ligature and ambitus
cause segfault
http://code.google.com/p/lilypond/issues/detail?id=1715
Backported (including updates to regtest in
c44c6048c3075c8a4fe5202777f048c6d66d5202 and
684cee4c6b41a4df5943b5a5a999a36466bbe6f5 )
Commit is
Updates:
Labels: -backport fixed_2_14_2
Comment #9 on issue 1750 by carl.d.s...@gmail.com: Documentation
suggestion: transposition resulting in triple accidentals
http://code.google.com/p/lilypond/issues/detail?id=1750
Backported.
Commit 2e9ca19be5c7b4001c89281c02006e799c1709d1
Comment #1 on issue 1757 by n.putt...@gmail.com: Footnotes cannot attach to
many layout objects/grobs
http://code.google.com/p/lilypond/issues/detail?id=1757
Clefs
Barlines
Key signatures
Don't these work if you add the Footnote_engraver to the Staff context?
Comment #2 on issue 1757 by mts...@gmail.com: Footnotes cannot attach to
many layout objects/grobs
http://code.google.com/p/lilypond/issues/detail?id=1757
True that - sorry for having forgotten this!
___
bug-lilypond mailing list
Comment #3 on issue 1757 by n.putt...@gmail.com: Footnotes cannot attach to
many layout objects/grobs
http://code.google.com/p/lilypond/issues/detail?id=1757
It's probably harmless to add it by default, seeing as the engraver only
picks up grobs which are created in the context where it's
Graham Percival wrote Wednesday, July 13, 2011 6:06 PM
Or, if there's serious oppositition to keeping this font in
lilypond itself, then at least provide the mechanism to change
fonts, and then James+company can add his own metafont font (the
bits from 2.14.0) from some separate archive site.
Updates:
Labels: Patch-new
Comment #9 on issue 1688 by carl.d.s...@gmail.com: New half-closed hihat
symbol for drum mode
http://code.google.com/p/lilypond/issues/detail?id=1688
Patch uploaded for review
http://codereview.appspot.com/4714043/
To regenerate the font, you will need to
Comment #2 on issue 1739 by colinpkc...@gmail.com: doc: correcting note
about rerunning regtests
http://code.google.com/p/lilypond/issues/detail?id=1739
This has had its countsown; please mark fixed with the commit message from
the patch.
___
Updates:
Owner: lemniska...@gmail.com
Comment #1 on issue 1736 by colinpkc...@gmail.com: clarify description of
minimal examples
http://code.google.com/p/lilypond/issues/detail?id=1736
This has had its countdown; please mark as fiuxed and quote the commit
message from the patch.
32 matches
Mail list logo
