-offset (which ignores the *invisible wall*)
can be a quite correct workaround.
Clément Ryder
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
I'm not top posting.
Hello,
Using oneVoice position (or indirectly, partcombineApart) while making a beam
go
over a rest destroys vertical alignment in a staff.
Here is a small example, with or without manual beaming over the rest.
%%%
\version 2.17.13
\relative c'' {
\voiceOne
I'm not top posting.
Hello,
PartcombineApart refuses Rest's overrides.
In the first Voice, it does nothing. In the second Voice, it crashes.
When Rests are merged, no problem.
This bug does not affect MultiMeasureRests.
\version 2.17.3
partI = \relative c'' {
\partcombineApart
\override
Hi,
Thanks for your answer !
Le 28 mars 2012 00:18, Colin Hall colingh...@gmail.com a écrit :
On Mon, Mar 26, 2012 at 11:08:51PM +, Clément wrote:
Hello,
I've encountered many limits when trying to put numbers above measures.
Thanks very much for the bug report, Clement.
I've
Le 28 mars 2012 10:16, Colin Hall colingh...@gmail.com a écrit :
On Wed, Mar 28, 2012 at 12:59:00AM +0200, Xavier Scheuer wrote:
On 28/03/2012, Colin Hall colingh...@gmail.com wrote:
Looking at that horn part I only see the number 1 above single bar
rests.
So, does the following
Hello,
I've encountered many limits when trying to put numbers above measures.
2 problems :
1) I found no possibility to print number 1 above multi-measure rests.
This is no crazy idea of mine, Breitkopf does it :
http://erato.uvt.nl/files/imglnks/usimg/f/ff/IMSLP11706-Mozart-
Changing global text size (only text!) is currently impossible.
If I use a new font (instead of the repetitive lilypond's default font),
this new font may be smaller than the default font, then I must change each
markup's size.
Changing default font size by making a new font tree also changes
