staccato dot in beam
I'm not top posting.
The following example prints the staccato-dot too close to the beam.
This could be solved in two ways:
1. print the staccato dot centered above the stem rather than the notehead
2. check for collisions with beams and increase the dot distance a little
\version 2.11.6
\layout { ragged-right = ##t }
{ d''1 } \\ { r4 b'8-. b-. r2 }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 212 in project lilypond
Issue 212: Context-initial afterGrace generates programming error http://code.google.com/p/lilypond/issues/detail?id=212 Comment #1 by hanwenn: fix the input. You need \new Voice iso. \new Staff Issue attribute updates: Status: Invalid -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 129 in project lilypond
Issue 129: tuplet bracket gets extended with partcombine http://code.google.com/p/lilypond/issues/detail?id=129 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_8 fixed_2_11_8 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 197 in project lilypond
Issue 197: problem with lilypond-book naming schemes with multiple \scores http://code.google.com/p/lilypond/issues/detail?id=197 Comment #2 by hanwenn: correction: 2.11.8 Issue attribute updates: Labels: fixed_2_11_8 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 150 in project lilypond
Issue 150: rests under beams not positioned well with \voiceXXX http://code.google.com/p/lilypond/issues/detail?id=150 Comment #1 by hanwenn: #136 Issue attribute updates: Status: Duplicate -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 135 in project lilypond
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #1 by hanwenn:
Disagree about this being a bug.
emptyText sets constraints ('rods').
In the absence of anything else (ie. notes), lily
has to use some basis for guessing a space. It does
so by taking the width of the papercolumn object,
which is wide due to the fooo text.
---gt;8
\version quot;2.9.28quot;
\layout{
indent=0.
line-width=3.\cm}
\relative c' {
\emptyText
c1\noBreak
s1^\markup{quot;fquot;}
c1
}
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 197 in project lilypond
Issue 197: problem with lilypond-book naming schemes with multiple \scores http://code.google.com/p/lilypond/issues/detail?id=197 Comment #3 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Text scripts on spacer notes. Was: Issue 135 in project lilypond
Can we turn this into a question: What's the best way to specify that a
TextScript attached to a spacer note does not occupy any horizontal space
(meaning that the bar lines are placed at the same place as if you
didn't have
the text)?
The best I can come up with is
\override TextScript #'X-extent = #'(0 . 0)
However, this means that it isn't taken into account in the new fancy
collision avoidance.
A common situation where this is useful is when you have a tempo change
at a bar line and the instrumental part begins with a multi measure rest.
The following example illustrates four different solutions. The last one
is the only one that gives a really nice output, but I find it a bit
embarrasing
for LilyPond that you can't get this layout without using such an ugly hack.
\version 2.10.0
\relative c''' {
c1
% Nice handling of the text but wrong rest.
r1^\markup{Andante molto}
c1
% The text affects the bar lines
R1 s1^\markup{Andante molto}
c1
% Better, but the collision handling doesn't work
\once \override TextScript #'X-extent = #'(0 . 0)
R1 s1^\markup{Andante molto}
c1
% Desired layout, but ugly tweaks in the input:
R1 \once \override Rest #'transparent = ##t r1^\markup{Andante
molto}
c1
}
/Mats
[EMAIL PROTECTED] wrote:
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #1 by hanwenn:
Disagree about this being a bug.
emptyText sets constraints ('rods').
In the absence of anything else (ie. notes), lily has to use some
basis for guessing a space. It does
so by taking the width of the papercolumn object,
which is wide due to the fooo text.
---gt;8
\version quot;2.9.28quot;
\layout{
indent=0. line-width=3.\cm}
\relative c' {
\emptyText
c1\noBreak
s1^\markup{quot;fquot;}
c1
}
Issue attribute updates:
Status: Invalid
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 197 in project lilypond
Issue 197: problem with lilypond-book naming schemes with multiple \scores http://code.google.com/p/lilypond/issues/detail?id=197 Comment #1 by hanwenn: Can you recheck 2.10.8, where I have made some changes in the lp-book output routines? All scores will be output. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 58 in project lilypond
Issue 58: polyphonic Rest #'position should only be set if other voice is printing http://code.google.com/p/lilypond/issues/detail?id=58 Comment #7 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 104 in project lilypond
Issue 104: emptyText doesn't work with lyricmode http://code.google.com/p/lilypond/issues/detail?id=104 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 122 in project lilypond
Issue 122: stemlet beams incorrect angle http://code.google.com/p/lilypond/issues/detail?id=122 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 136 in project lilypond
Issue 136: incorrect default rest position for upper voice if under a beam http://code.google.com/p/lilypond/issues/detail?id=136 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 176 in project lilypond
Issue 176: programming error: strict-note-spacing together with \afterGrace http://code.google.com/p/lilypond/issues/detail?id=176 Comment #9 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 184 in project lilypond
Issue 184: bad tremolo positioning when stem-direction is forced http://code.google.com/p/lilypond/issues/detail?id=184 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 192 in project lilypond
Issue 192: clef change in second staff stops tie in first staff http://code.google.com/p/lilypond/issues/detail?id=192 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 200 in project lilypond
Issue 200: lyric placement not consistent http://code.google.com/p/lilypond/issues/detail?id=200 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 207 in project lilypond
Issue 207: Rhythm moves afterGrace to incorrect measure http://code.google.com/p/lilypond/issues/detail?id=207 Comment #4 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 208 in project lilypond
Issue 208: \repeat does not take identifier http://code.google.com/p/lilypond/issues/detail?id=208 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 213 in project lilypond
Issue 213: progerror \bendAfter
http://code.google.com/p/lilypond/issues/detail?id=213
New issue report by gpermus:
bug.ly:8:9: warning: programming error: bounds of this piece aren't breakable.
f4.
-\bendAfter #+1
\version quot;2.11.7quot;
\score {
lt;lt;
\new Voice \relative c' {
\time 4/4
g''4.-\bendAfter #+1
s8 s2
f4.-\bendAfter #+1
}
gt;gt;
}
\paper {
ragged-right = ##t
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-High
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 125 in project lilypond
Issue 125: progerror \bendAfter collision http://code.google.com/p/lilypond/issues/detail?id=125 Comment #4 by gpermus: Err... ok. Reported as bug 213. This particular report is therefore closed. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 127 in project lilypond
Issue 127: Dead contexts keep making an influence to the end of the line http://code.google.com/p/lilypond/issues/detail?id=127 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 31 in project lilypond
Issue 31: modern-cautionary incorrectly marks some accidentals as cautionary http://code.google.com/p/lilypond/issues/detail?id=31 Comment #2 by gpermus: I'm sure this was fixed by Rune's accidental patch from Dec 17. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 32 in project lilypond
Issue 32: use skyline spacing for rods between notes. http://code.google.com/p/lilypond/issues/detail?id=32 Comment #5 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 150 in project lilypond
Issue 150: rests under beams not positioned well with \voiceXXX http://code.google.com/p/lilypond/issues/detail?id=150 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 197 in project lilypond
Seems to work fine! As a by product, there's no longer any need to add a \book block around the input if you have several \score and/or \markup in the same lilypond snippet. If this indeed is the intended behaviour (which I think is great), I'll update the manual correspondingly. /Mats [EMAIL PROTECTED] wrote: Issue 197: problem with lilypond-book naming schemes with multiple \scores http://code.google.com/p/lilypond/issues/detail?id=197 Comment #1 by hanwenn: Can you recheck 2.10.8, where I have made some changes in the lp-book output routines? All scores will be output. -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 193 in project lilypond
Issue 193: collision accidental fingering http://code.google.com/p/lilypond/issues/detail?id=193 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_8 fixed_2_11_8 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 213 in project lilypond
Issue 213: progerror \bendAfter http://code.google.com/p/lilypond/issues/detail?id=213 Comment #1 by hanwenn: why is this priority high? Issue attribute updates: Labels: -Priority-High Priority-Low -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 213 in project lilypond
[EMAIL PROTECTED] wrote: Issue 213: progerror \bendAfter http://code.google.com/p/lilypond/issues/detail?id=213 Comment #1 by hanwenn: why is this priority high? My understanding was that all progerrors were high. Evidently it's just crashes that are high; progerrors with good output are low? - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 213 in project lilypond
Graham Percival escreveu: [EMAIL PROTECTED] wrote: Issue 213: progerror \bendAfter http://code.google.com/p/lilypond/issues/detail?id=213 Comment #1 by hanwenn: why is this priority high? My understanding was that all progerrors were high. Evidently it's just crashes that are high; progerrors with good output are low? correct. If you want to know why, have a look at the 'make web' output. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
