Pierre Perol-Schneider | 19 Dec 13:00 2014

LSR: Printing figured bass extender lines without a starting figure

Hi BugList,

I've noticed that the snippet named "Printing figured bass extender lines
without a starting figure" is doubled :
- http://lsr.di.unimi.it/LSR/Item?id=607
- http://lsr.di.unimi.it/LSR/Item?id=788
Any reason ?
If none, wich one should be removed ?

Paul Morris | 17 Dec 20:23 2014

Update guile version dependency info in docs from "1.8.2 or newer" to "1.8.2"

In the docs, update dependency info from guile “(1.8.2 or newer)” to just “(1.8.2)” until guile
2.0 support is stable.  As reported on the user list here:

http://lilypond.1069038.n5.nabble.com/Kubuntu-GCC-compile-with-guile-2-td169498.html <http://lilypond.1069038.n5.nabble.com/Kubuntu-GCC-compile-with-guile-2-td169498.html>

I did a cursory web search and found these two instances. There may be


http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#requirements-for-running-lilypond <http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#requirements-for-running-lilypond>

bug-lilypond mailing list
bug-lilypond <at> gnu.org
Keith OHara | 14 Dec 05:43 2014

Re: 2 Table of contents in same source file

Added as
Dan Eble | 13 Dec 17:24 2014

"voice" accidental style

The Notation Reference explains that the “voice” accidental style might not provide what one wants. 
That is true in my experience.  Even pieces meant to be performed a capella are sometimes rehearsed with the
help of a keyboard player.  (Sometimes they are even performed that way :-( )  The "modern-voice" and
"modern-voice-cautionary" styles provide cross-voice cancellations, but most of the time I’d
rather not see the cancellations they add following a bar line.

What do you think of renaming the current “voice” style to something like “voice-only” and adding
new styles “voice” and “voice-cautionary” that provide cross-voice cancellations without
the other “modern” features?

bug-lilypond mailing list
bug-lilypond <at> gnu.org
Knute Snortum | 8 Dec 19:27 2014

Some C9 chords should be Cadd9

Way back in Lilypond 2.14 if you wrote c:9^7 you would get "Cadd9", but now
you get "C9".  This makes it indistinguishable from c:9.

I propose that c:9^7 should render as "Cadd9".  See code and attached
proposed output.

\version "2.19.15"

\score {
  \new ChordNames \chordmode {
  \layout {

Knute Snortum
(via Gmail)
bug-lilypond mailing list
bug-lilypond <at> gnu.org
Eugene Cormier | 7 Dec 06:05 2014

grace + multiple staves = multiple time sigs

> I'm not top posting.

I'm pretty sure you guys already know about this, but I can't seem to find it 
on the bug tracker.

If you have multiple staves with a time sig change and grace at the same time 
we get duplicated time sigs:

  \new Staff { \time 4/4 c''1 \time 3/4 c''2. }
  \new Staff { \time 4/4 c''1 \time 3/4 \grace b'8 c''2. }

For now I've been getting around the problem by putting the time sig change 
in only the staff with the grace

  \new Staff { \time 4/4 c''1 c''2. }
  \new Staff { \time 4/4 c''1 \time 3/4 \grace b'8 c''2. }

But obviously this will cause problems in a larger work with score and parts

Dan McMahill | 7 Dec 04:57 2014

footnotes in markup attached to notes not working

> I'm not top posting.

% The first footnote works as expected.
% the second doesn't.  The second puts the * in the markup bu
% doesn't actually create the footnote.

% Checked with version 2.19.15

\version "2.19.15"

% test 1
\markup{ \italic "(rit.)" \footnote "*" \italic "* First note about the rit." }

hornA = \relative c' {
  \key a \major
  \time 3/4 
  a4 a a | 
  % test 2
  a_\markup{ \italic "(rit.)" \footnote "*" \italic "* Second note about the
rit." } 
   a a |

hornPartA = \new Staff \with {
  %instrumentName = "Horn in F"
  midiInstrument = "french horn"
} {\transposition f \hornA }

\score {
(Continue reading)

Eugene Cormier | 7 Dec 04:59 2014

footnotes should work on markup attached to a note

Hey guys,

this works:
{ \markup { "rit" \footnote "*" "* text" }

this does not:
{ c4_\markup { "rit" \footnote "*" "* text" } }

should it? I think so...

(tested on lilypond v2.18)
Urs Liska | 6 Dec 07:59 2014

Fwd: 3 new lilypond issues

forwarding ...

-------- Ursprüngliche Nachricht --------
Von: Jan Hakenberg <jan.hakenberg <at> gmail.com>
Gesendet: 6. Dezember 2014 07:35:15 MEZ
An: James <pkx166h <at> gmail.com>
CC: Urs Liska <ul <at> openlilylib.org>
Betreff: 3 new lilypond issues


I briefly searched the "open issues", but did not find the below
suggestions/observations listed.

My Platform: Windows 7
LilyPond: 2.19.15

1) ----------------------------

In the docs
"LilyPond Application Usage  1.2 Command-line usage"
the command line parameter "-dclip-systems"
is explained by
"Generate cut-out snippets of a score."

I think it would be helpful to add a remark that this parameter has no
effect unless
"clip-regions" are specified in the ly file.

Also, it might be worth mentioning that for the export to happen, the status
(Continue reading)

Dan Eble | 1 Dec 03:01 2014

Rest-dot spacing

Is it expected that these two ways of changing the appearance of a rest yield different spacing between the
rest and the dot?

\version "2.19.15"

classicalQuarter = #(lambda (grob)
  (if (= (ly:grob-property grob 'duration-log 999) 2)
      (ly:grob-set-property! grob 'style 'classical))
  (ly:rest::print grob))

  \new Staff {
    \override Rest #'style = #'classical r4.

  \new Staff {
    \override Rest #'stencil = \classicalQuarter r4.
Pierre Perol-Schneider | 30 Nov 15:36 2014

LSR : Changing the font to small caps

Hi Squad,

See : http://lsr.di.unimi.it/LSR/Item?id=100
where smallCaps don't show up.
So I'd like to change it to :

  \relative c'' { c4 c c8 c c }
  \addlyrics { what is \markup\caps { The } Ma -- trix?  }

Any objection ?