The following code compiles without errors, but the flat sign in the
chord name does not appear.
\version "2.11.18"
\header { title = "Whereditgo?" }
\score {
<<
\override Score.ChordName #'font-name = #"Arial"
\new ChordNames { \chordmode { aes1 }
\relative c' { c
Graham Percival wrote:
Paul Scott wrote:
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=324
The bug you recorded is not the primary bug I was reporting and as I
noted doesn't even happen in a normal part.
The bug is that the "stems" or flags for b
Issue 312: minimum-Y-extent is ignored in vertical spacing
http://code.google.com/p/lilypond/issues/detail?id=312
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
Issue 312: minimum-Y-extent is ignored in vertical spacing
http://code.google.com/p/lilypond/issues/detail?id=312
Comment #3 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
--
You received this message because you are listed in the owner
or
Issue 295: non-horizontal beam-slope for stretched stems.
http://code.google.com/p/lilypond/issues/detail?id=295
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or
Issue 258: microtonal shift should be undone before next note
http://code.google.com/p/lilypond/issues/detail?id=258
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 own
Paul Scott wrote:
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=324
The bug you recorded is not the primary bug I was reporting and as I
noted doesn't even happen in a normal part.
The bug is that the "stems" or flags for both voices are up and co
Issue 318: whole note angled tremolo
http://code.google.com/p/lilypond/issues/detail?id=318
Comment #2 by gpermus:
This might be related:
% The "stems" or flags for both voices are up and collide where the
% "stems" for the lower voice should be down.
\version "2.11.20"
clm= \relative c''
Arvid Grøtting wrote:
2007/2/28, Graham Percival <[EMAIL PROTECTED]>:
I can't reproduce this (even after uncommenting that line) with 2.11.20
on OSX. Could you check that you attached the right file?
I did. Are you sure you're not seeing a difference? I've attached
PNGs of the two different
Issue 325: system-count stops stretching
http://code.google.com/p/lilypond/issues/detail?id=325
New issue report by gpermus:
\version "2.11.20"
\paper {
%% uncomment next line, and stretching disappears.
%% system-count = 3
ragged-last-bottom = ##f
}
\score {
\context Score <<
\re
Graham Percival wrote:
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=324
I don't think it's related to 318, since this problem persists if we
use half notes instead of whole notes.
The bug you recorded is not the primary bug I was reporting and as I
noted doesn't even hap
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=324
I don't think it's related to 318, since this problem persists if we use
half notes instead of whole notes.
Cheers,
- Graham
Mats Bengtsson wrote:
This seems to be related to
http://code.google.com/p/lilypond/issues/deta
Issue 324: tremolo divisi causes new \Staff context to appear
http://code.google.com/p/lilypond/issues/detail?id=324
New issue report by gpermus:
% problem disappears if \new Staff is made explicit.
\version "2.11.20"
clm= \relative c'' { \repeat tremolo 4 { e16( cis) } }
clma = \relative
2007/2/28, Graham Percival <[EMAIL PROTECTED]>:
I can't reproduce this (even after uncommenting that line) with 2.11.20
on OSX. Could you check that you attached the right file?
I did. Are you sure you're not seeing a difference? I've attached
PNGs of the two different results I get...
I k
Issue 322: default whole / half rest size too large
http://code.google.com/p/lilypond/issues/detail?id=322
Comment #1 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fi
Thanks, entered as
http://code.google.com/p/lilypond/issues/detail?id=323&can=2&q=
Cheers,
- Graham
Stan Sanderson wrote:
\version "2.10.20"
\layout {ragged-right = ##t}
sfoL = \set fingeringOrientations = #'(left)
sfoR = \set fingeringOrientations = #'(right)
sfoU = \set fingeringOrientations
I can't reproduce this (even after uncommenting that line) with 2.11.20
on OSX. Could you check that you attached the right file?
Cheers,
- Graham
Arvid Grøtting wrote:
Arvid Grøtting gmail.com> writes:
I haven't cooked up a minimal example yet, but is vertical stretching supposed
to disa
Issue 322: default whole / half rest size too large
http://code.google.com/p/lilypond/issues/detail?id=322
New issue report by scottmillercomposer:
\version "2.11.20"
\header {
texidoc = "Default whole and half rest size seems proportionally
too large"
}
\layout { ragged-right=##t }
\re
Issue 320: ancient mensural accidentals swapped
http://code.google.com/p/lilypond/issues/detail?id=320
Comment #1 by gpermus:
Err, that previous message was
> Werner
Juergen
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred thi
Issue 320: ancient mensural accidentals swapped
http://code.google.com/p/lilypond/issues/detail?id=320
New issue report by gpermus:
> [lilypond 2.11.20]
>
> Looking at section 7.7.12, `Mensural contexts', it seems to me that
> the sharp and flat accidentals are intermixed. The `fis' looks like
>
Mats Bengtsson wrote:
This seems to be related to
http://code.google.com/p/lilypond/issues/detail?id=318
I forward it to bug-lilypond.
Thanks. Sorry I didn't have time to do more research on the bug this
morning.
The "line feed" goes away if you use
\new Staff {
\clm \clma << \clm \\ \clma >
Issue 97: request: center mark over bar sign (instead of the right edge)
http://code.google.com/p/lilypond/issues/detail?id=97
Comment #3 by lemzwerg:
A solution to this problem is probably to introduce an `anchor'
for markups which is located horizontally in the optical center
of the bar glyph in
Issue 319: metronome as a scheme number
http://code.google.com/p/lilypond/issues/detail?id=319
Comment #1 by gpermus:
Sorry, feature already available.
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields of this issue,
\version "2.10.20"
\layout {ragged-right = ##t}
sfoL = \set fingeringOrientations = #'(left)
sfoR = \set fingeringOrientations = #'(right)
sfoU = \set fingeringOrientations = #'(up)
sfoD = \set fingeringOrientations = #'(down)
\relative c'' {
\sfoR < a-1 d-2>4
\sfoL < a-1 d-2>
This seems to be related to
http://code.google.com/p/lilypond/issues/detail?id=318
I forward it to bug-lilypond.
The "line feed" goes away if you use
\new Staff {
\clm \clma << \clm \\ \clma >>
}
But I don't understand why it happens. It somehow
seems related to the fact that you have separate
\
Arvid Grøtting gmail.com> writes:
> I haven't cooked up a minimal example yet, but is vertical stretching supposed
> to disappear if you set system-count to a value in the \paper block?
\version "2.11.20"
\paper {
%% uncomment next line, and stretching disappears.
%% system-count = 3
ragg
Issue 97: request: center mark over bar sign (instead of the right edge)
http://code.google.com/p/lilypond/issues/detail?id=97
Comment #1 by lemzwerg:
The problem still exists, except that the default positioning
of rehearsal marks has been changed -- it's actually worse than
before...
Here my te
I haven't cooked up a minimal example yet, but is vertical stretching supposed
to disappear if you set system-count to a value in the \paper block?
--
Arvid
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bu
See http://lists.gnu.org/archive/html/lilypond-user/2007-02/msg00558.html
/Mats
François VION wrote:
Bonjour,
Je viens juste d'installer Lilypond version 2.11.20 un Macbook Intel Mac Os X
sous Tiger.
Quand j'essaye de compiler le fichier ouvert par défault à la première ouverture
de Lilypond
Bonjour,
Je viens juste d'installer Lilypond version 2.11.20 un Macbook Intel Mac Os X
sous Tiger.
Quand j'essaye de compiler le fichier ouvert par défault à la première ouverture
de Lilypond "a scale in lilypond" j'obtiens le rapport d'erreur suivant
Traitement de << /Users/francoisvion/Desktop/e
30 matches
Mail list logo
