\version "2.14.1"
%The bass clef in the lower staff is placed to the left of the staff. If either
%the tempo mark is removed or the triplets are changed to a quarter note the
%the clef is placed correctly. This was not an error in 2.12.3.
musx = \relative c'
{
% Change this to c4 for correct cl
On Tue, Jun 14, 2011 at 11:55 PM, Jay Anderson wrote:
> \version "2.14.1"
>
> %The bass clef in the lower staff is placed to the left of the staff. If
> either
> %the tempo mark is removed or the triplets are changed to a quarter note
> the
> %the clef is placed correctly. This was not an error i
On Wed, Jun 15, 2011 at 6:11 AM, Ralph Palmer wrote:
> This has been submitted as Issue 1695 :
> http://code.google.com/p/lilypond/issues/detail?id=1695
Thanks. I think I found a couple workarounds:
musy = \relative c'
{
\clef treble
\override Score.NonMusicalPaperColumn #'allow-loose-spaci
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1695 by ralphbug...@gmail.com: Clef change placed outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
I cannot confirm this problem. No matter how I try to open or edit the .ly
file (in ConTEXT or in
Updates:
Labels: -Priority-High Priority-Critical Regression
Comment #1 on issue 1695 by philehol...@googlemail.com: Clef change placed
outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
Confirmed on my windows box. Regression occurred between 2.13.31 and 13.34
Comment #2 on issue 1695 by reinhold...@gmail.com: Clef change placed
outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
I can confirm it too, here on linux.
If the regression occurred between 2.13.31 and .34, then my bet is that
Jan's work on the Metronome-mark (a
Comment #3 on issue 1695 by percival.music.ca: Clef change placed outside
score
http://code.google.com/p/lilypond/issues/detail?id=1695
the problem occurred between
BAD:
9a63326816f586dd79d326776583697f95203330
and GOOD:
d3d40f3469eda2cb327bebbd392c1ce88b114394
but unfortunately the
Comment #4 on issue 1695 by n.putt...@gmail.com: Clef change placed outside
score
http://code.google.com/p/lilypond/issues/detail?id=1695
1d4914c023a672e0e80b9b9eafc123605f4c0f00 is the first really bad commit (my
initial commit is also a bit weird, but it's the tempo mark whi
Updates:
Status: Started
Owner: n.putt...@gmail.com
Comment #5 on issue 1695 by n.putt...@gmail.com: Clef change placed outside
score
http://code.google.com/p/lilypond/issues/detail?id=1695
(No comment was entered for this change
Updates:
Labels: Patch-review
Comment #6 on issue 1695 by n.putt...@gmail.com: Clef change placed outside
score
http://code.google.com/p/lilypond/issues/detail?id=1695
Patch: http://codereview.appspot.com/4683043/
___
bug-lilypond mailing
Updates:
Labels: CD-110718
Comment #7 on issue 1695 by colinpkc...@gmail.com: Clef change placed
outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Status: Fixed
Labels: -Patch-review -CD-110718 fixed_2_15_6 backport
Comment #8 on issue 1695 by n.putt...@gmail.com: Clef change placed outside
score
http://code.google.com/p/lilypond/issues/detail?id=1695
bebd93c2dd0d7363f311d912ec1ed1f7dfcb36ba
Updates:
Labels: -backport fixed_2_14_2
Comment #9 on issue 1695 by carl.d.s...@gmail.com: Clef change placed
outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
Backported
___
bug-lilypond mailing list
bug-lilypond
Comment #10 on issue 1695 by carl.d.s...@gmail.com: Clef change placed
outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
Backported
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug
Updates:
Status: Verified
Comment #11 on issue 1695 by philehol...@googlemail.com: Clef change placed
outside score
http://code.google.com/p/lilypond/issues/detail?id=1695
(No comment was entered for this change.)
___
bug-lilypond mailing
15 matches
Mail list logo
