PKX wrote:
>
>
> However in the next section where there is an alternate volta section, the
> bar
> after the first repeat is broken incorrectly (as I see it) and I get a bar
> check failure. I am expecting it to put a bar before the last dotted
> minim.
>
>
Hi Pete
if i understand correc
Updates:
Labels: -Priority-Regression Priority-Medium
Comment #2 on issue 899 by n.puttock: full-measure-extra-space should be
more flexible
http://code.google.com/p/lilypond/issues/detail?id=899
I've changed the priority since this was a deliberate change in 2.11.10.
--
You received
Updates:
Status: Started
Labels: -fixed_2_13_9
Comment #6 on issue 787 by n.puttock: script stack order fails with 2 more
notes
http://code.google.com/p/lilypond/issues/detail?id=787
This is still not quite right, as Reinhold has found out with the regtest
accidental-suggestio
P. Kayex wrote:
I start with a partial and I have a volta 2 section (with no alternate) and
the next bar after the repeat is 'measured' correctly from the preceding bar.
However in the next section where there is an alternate volta section, the bar
after the first repeat is broken incorrectly (
> I'm not top posting.
Hello, I am struggling with understanding if this is a bug or I am doing
something wrong. I have looked in the bug tracker and cannot see anything.
I have included a small snippet.
I start with a partial and I have a volta 2 section (with no alternate) and
the next bar a
On Mon, Nov 30, 2009 at 5:43 PM, Robin Bannister wrote:
> 821's priority should therefore be not Medium but Regression.
Thanks, updated.
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lil
Updates:
Summary: Regression: arpeggios may collide with barlines in a PianoStaff
with multiple voices
Labels: -Priority-Medium Priority-Regression
Comment #1 on issue 821 by v.villenave: Regression: arpeggios may collide
with barlines in a PianoStaff with multiple voices
http://co
Robin Bannister wrote:
This of course also applies to the issue(s) I referenced in my followup
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00294.html
I am unsuccessful again. I will just spell out the main point:
The collision snippet which is registered as issue 821
http://co
\paper { ragged-right = ##t }
{% seen with versions 2.12.1, 2.10.33, 2.8.8
<< b'1 \\ s1 \\ 1 \arpeggio >> % arpeggio collides with voice1
}% unless there is an accidental (in any voice)
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu
\paper { ragged-right = ##t }
teeny = \set fontSize = #-3
<< % seen with versions 2.12.1, 2.10.33, 2.8.8
a'2
\\
% \once \override NoteHead #'X-extent = #'(0 . 1.3) % crude workaround to avoid
\teeny a'4 % voice2 colliding with larger voice1
It looks like the collision avoidance is pos
Updates:
Summary: Enhancement: instrument-aware presets (ambitus improvement?)
Comment #1 on issue 914 by v.villenave: Enhancement: instrument-aware
presets (ambitus improvement?)
http://code.google.com/p/lilypond/issues/detail?id=914
As Mats pointed out, this feature could be built o
Updates:
Status: Invalid
Comment #2 on issue 906 by v.villenave: gs fails in jail mode unless run
separately with sudo (error 32512)
http://code.google.com/p/lilypond/issues/detail?id=906
As you wish. Feel free to give me a ping if you stumble upon this again.
--
You received this me
Comment #1 on issue 918 by v.villenave: Enhancement:
\RemoveEmpty*StaffContext for all appropriate contexts
http://code.google.com/p/lilypond/issues/detail?id=918
I almost forgot: this request was made on the -fr list by Philippe Massart
and Xavier
Scheuer, but was also discussed previousl
Status: Accepted
Owner: v.villenave
CC: Carl.D.Sorensen
Labels: Type-Enhancement Priority-Medium Usability
New issue 918 by v.villenave: Enhancement: \RemoveEmpty*StaffContext for
all appropriate contexts
http://code.google.com/p/lilypond/issues/detail?id=918
%% There are currently shortcuts
Comment #1 on issue 906 by fodber: gs fails in jail mode unless run
separately with sudo (error 32512)
http://code.google.com/p/lilypond/issues/detail?id=906
I think this defect can be closed as invalid. This is most probably caused
by bad
configuration of libraries, as on a different machi
Comment #1 on issue 899 by v.villenave: full-measure-extra-space should be
more flexible
http://code.google.com/p/lilypond/issues/detail?id=899
See also issue 915 and issue 917.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starre
Comment #2 on issue 915 by v.villenave: Multi-measure rests dependent on
prefatory matter in other staves
http://code.google.com/p/lilypond/issues/detail?id=915
See also issue 917 and Issue 899.
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
On Mon, Nov 30, 2009 at 2:11 AM, Francisco Vila wrote:
> The best line is that which contains notes; others have a first
> measure overgrown.
Thanks, added as 917. See also Patrick's newly-added 915, that seems related.
Cheers,
Valentin
___
bug-lilyp
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Regression Engraving-nitpick
New issue 917 by v.villenave: Regression: Full-bar rests take more space at
the beginning of a line
http://code.google.com/p/lilypond/issues/detail?id=917
New report from Francisco:
% In the followi
Comment #1 on issue 915 by pnorcks: Multi-measure rests dependent on
prefatory matter in other staves
http://code.google.com/p/lilypond/issues/detail?id=915
After further testing, this happened between 2.11.27 and 2.11.28.
There were many commits between these two releases, but only two touc
20 matches
Mail list logo
