This is sort of a repeat from many months ago. It might be a bug; it
might not.
Try running the snippet below. The result is that \mark on the top
line is placed as expected; \mark attached to GrandStaff is pushed
way too far to the left. Any attempt to manipulate the second \mark's
posit
Hello
I don't know what is the problem here.
I have a foo.tex file that includes around 18 foo.ly files like this ;
\chapter{Les Motets}
\cleardoublepage
\lilypondfile[quote,noindent]{orig/1.ly}
\cleardoublepage
\lilypondfile[quote,noindent]{orig/2.ly}
LilyPond 2.11.13, Linux
Notes
-
Expected result: visible tie between the C's (top note) of the second
and third chords (the first two chords of the second measure).
Actual result: tie exists (if chords were spaced farther apart
horizontally it would be seen) but is not visible by default. Th
Issue 175: dashed line after \break too near to the staff
http://code.google.com/p/lilypond/issues/detail?id=175
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_14 fixed_2_10_14
--
You received this mess
Issue 179: broken text spanners don't end at same horizontal position
http://code.google.com/p/lilypond/issues/detail?id=179
Comment #4 by hanwenn:
#174 - to check this, use non-dashed lines
Issue attribute updates:
Status: Duplicate
--
You received this message because you are listed
Issue 179: broken text spanners don't end at same horizontal position
http://code.google.com/p/lilypond/issues/detail?id=179
Comment #3 by lemzwerg:
Oops, sorry!
I mean horizontal, not vertical.
Issue attribute updates:
Summary: broken text spanners don't end at same horizontal position
Werner LEMBERG escreveu:
>> nowadays, I push to the hwn branch, which I occasionally sync with
>> master.
>
> Why that? Such kind of bug fixes isn't experimental, isn't it?
because I'm lazy. Pushing a single commit to a different branch means
I have to check out that branch, cherry pick, recompi
Issue 179: broken text spanners don't end at same vertical position
http://code.google.com/p/lilypond/issues/detail?id=179
Comment #2 by hanwenn:
don't understand exactly: do you want the 2nd system 1st cresc to be lower, or
the
2nd cresc to be higher? or the 1st system?
--
You received this
Issue 253: 2.11.13 bus error
http://code.google.com/p/lilypond/issues/detail?id=253
Comment #5 by trevorbaca:
Could be very true that the glissando-over-pageBreak differs from the bus error
I was
getting with my original score (because the original score is 3600 lines). I
don't
have git access (
> nowadays, I push to the hwn branch, which I occasionally sync with
> master.
Why that? Such kind of bug fixes isn't experimental, isn't it?
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-li
Werner LEMBERG escreveu:
>> I fixed this,
>>
>> http://code.google.com/p/lilypond/issues/detail?id=255
>
> Did you? I miss it in git.
nowadays, I push to the hwn branch, which I occasionally sync with
master.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond
> I fixed this,
>
> http://code.google.com/p/lilypond/issues/detail?id=255
Did you? I miss it in git.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Jay Anderson escreveu:
> I see that issue 10 is closed
> (http://code.google.com/p/lilypond/issues/detail?id=10). However, I'm
> still seeing similar behavior. The attached is from the actual score.
> If I take out the accidentals it looks right. I can also remove the
> acciacatura from the low voi
Issue 255: main note left-matter may cover barline preceding grace note
http://code.google.com/p/lilypond/issues/detail?id=255
New issue report by hanwenn:
input/regression/spacing-horizontal-skyline-grace.ly
Issue attributes:
Status: Fixed
Owner: hanwenn
Labels: Type-
14 matches
Mail list logo
