Hi,
In the example in the documentation of 2.17.4 relating to
'outside-staff-padding, the last line of text ought to be close to the
previous text.
Compare:
2.16 -
http://www.lilypond.org/doc/v2.16/Documentation/notation/vertical-collision-avoidance
2.17.4 -
Hi,
Mike's commit d8dfa746ead381a80901106b9c9b079dc9b5d004 renamed gap
property (which was a number) to beam-gap (which is now a pair). This
is not documented anywhere. Also, no convert-ly rule was written.
cheers,
Janek
___
bug-lilypond mailing
Hello,
2012/10/14 Songmuh Jong song...@yahoo.com
I'm not top posting.
% duplicated tempo printed
% key signature appearsduped
% This only happens when the bass starts with \appoggiatura
This coresponds to Known issues and warnings in
Hello,
2012/10/15 Daniel Berjón asurancetu...@gmail.com
% Cross-staff arpeggios and dynamics collide.
\version 2.16.0
\new PianoStaff {
\set PianoStaff.connectArpeggios = ##t
{c' e' g'4\arpeggio}
\new Dynamics {r4\ff}
{c' e' g'4\arpeggio}
}
Thank
Hello,
2012/10/16 Nick Payne nick.pa...@internode.on.net
Going to the manual page for 2.16 ( http://lilypond.org/manuals.html)
and entering a search term (eg I tried footnote) in the search box at
upper right returns hits in the 2.17 manuals. The search presented to
Google is:
Hello,
2012/10/16 David Nalesnik david.nales...@gmail.com
In the example in the documentation of 2.17.4 relating to
'outside-staff-padding, the last line of text ought to be close to the
previous text.
Compare:
2.16 -
Hello,
2012/10/13 Federico Bruni fedel...@gmail.com
As you can see in the attached image, the pull-off sign (slur in TabStaff)
is moved up when using manual beaming.
It looks like Stems in default TabStaff are just made transparent when
using manual beams. Maybe the stem stencil should be
On Tue, Oct 16, 2012 at 09:02:18AM +0100, Phil Holmes wrote:
It's a common header, used on all the web pages, and therefore uses the same
version number throughout. Non-trivial to change.
Shouldn't it be v2.16, though? It's safer to point to v2.16
rather than v2.17.
- Graham
correction:
On Sat, 2012-10-13 at 09:28 +0100, Richard Shann wrote:
Hi,
I notice I did
*not*
give the result of the strings command on the pdf
generated from the Denemo-generated lilypond,
sorry about that
Richard
___
bug-lilypond mailing list
Hi,
I notice I did give the result of the strings command on the pdf
generated from the Denemo-generated lilypond, putting it into a file
called junk3.ly I get this session:
lilypond junk3.ly strings junk3.pdf | grep textedit
GNU LilyPond
Hi,
Thanks for the response.
With junk.ly consisting of exactly
{ c' c'\breathe c' c' }
then
lilypond junk.ly
creates a file junk.pdf with no point and click for the breathing sign.
The version is
lilypond --version
GNU LilyPond 2.12.3
I see no link when hovering over the breathing sign with
Sorry - my follow-up email was sent before your previous reply arrived
(I don't know where the emails are living in the meantime...). And sorry
for not reporting the version number initially that was very dumb. I'll
try and get a setup for testing against last stable lilypond instead of
what comes
2012/10/13 Richard Shann richard.sh...@virgin.net:
Sorry - my follow-up email was sent before your previous reply arrived
(I don't know where the emails are living in the meantime...). And sorry
for not reporting the version number initially that was very dumb. I'll
try and get a setup for
13 matches
Mail list logo
