Re: Changing volta number text
On Tue, May 18, 2021 at 1:11 PM Jean Abou Samra wrote:
>
> It is worth noting that the \volta command added by Dan Eble in the 2.23
> development series does exactly the job requested here, if I understood
> correctly.
>
> \version "2.23.2"
>
> \language english
>
> {
>\time 3/4
>\repeat volta 4
>{
> a'4 b' c' |
> b'4 c' d' |
>}
>\alternative {
> \volta 1,3 {
>e'4 f' g' |
> }
> \volta 2 {
>d'4 c' b' |
> }
> \volta 4 {
>g'4 a' b' |
> }
>}
>c'2.
> }
>
> Updated documentation is here:
>
>
> http://lilypond.org/doc/v2.23/Documentation/notation/long-repeats.html#alternative-endings
>
> Best,
> Jean
>
Wow! Thanks, Jean. Downloaded and (with some fits and starts) installed
2.23.2.
All the best,
Ralph
--
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Changing volta number text
On Tue, May 18, 2021 at 6:35 AM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Ralph,
>
> > I think it would be helpful to either have a snippet that shows how to
> change a "normal" volta number setup (i.e., change the numbers and/or add
> text), or to add something to the documentation.
>
> The documentation is accurate, if not entirely clear… =)
> This is what I got using <
> https://lilypond.org/doc/v2.21/Documentation/notation/long-repeats#manual-repeat-marks
> >:
>
> %%
> \version "2.21.0"
> \include "english.ly"
>
> test = {
> \time 3/4
> a'4 b' c' |
> b'4 c' d' |
> {
> {
> \set Score.repeatCommands = #'((volta "1., 3."))
> e'4 f' g' |
> }
> {
> \set Score.repeatCommands = #'(end-repeat (volta "2."))
> d'4 c' b' |
> }
> {
> \set Score.repeatCommands = #'(end-repeat (volta "4."))
> g'4 a' b' |
> \set Score.repeatCommands = #'((volta #f))
> }
> }
> c'1
> }
>
> \score {
> \test
> }
> %%%
>
> Note that I deleted the \repeat volta command, but kept the bracketing of
> your \alternative block for readability.
>
> Hope this helps!
> Kieren.
>>
>>
Thanks, Kieren.
I have to admit, after learning from you that the documentation is
accurate, and spending some time examining the various examples in the
documentation, I think I could achieve what I want. It takes some real
effort, and I think it would be difficult for someone who has little
experience with LilyPond. And isn't that the point of the documentation?
I've run into this problem before while doing transcription, and solved the
problem somehow, but I couldn't (can't) find the exact file where I used
the solution. I've also seen the pattern occasionally while playing music.
I think it would be helpful to include an appropriate example in the manual
repeat marks section of the documentation. Then again, this hasn't exactly
come up as a problem very often, has it? . . . I guess I'll make a note of
the solution!
All the best,
Ralph
--
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Changing volta number text
On Fri, May 14, 2021 at 7:26 PM Aaron Hill wrote:
> On 2021-05-14 6:40 pm, Ralph Palmer wrote:
> > Excellent! Thank you, Aaron. I wish I could understand what your
> > function
> > does - how it works.
>
> The technique involves querying the current Score.repeatCommands and
> replacing any existing (volta "...") command with the user-provided
> version. This preserves the other repeat commands such as (end-repeat)
> and (volta #f).
>
> Here is a minorly-refactored version with some documentation, comments,
> and a helpful usage warning:
>
>
> \version "2.22.0"
> \include "english.ly"
>
> changeVoltaText =
> #(define-music-function
>(text) (markup?)
>(_i "Replaces the volta text within the currently-set
> @code{repeatCommands}.")
>
>(define (volta-text? cmd)
> ;; Look for the (volta "...") pattern.
> (and (pair? cmd)
> (eq? 'volta (car cmd))
> (markup? (cadr cmd
>(define (replacer cmd)
> (if (volta-text? cmd) `(volta ,text) cmd))
>(define (proc ctxt)
> (let ((cmds (ly:context-property ctxt 'repeatCommands '(
> (if (any volta-text? cmds)
> (ly:context-set-property! ctxt 'repeatCommands (map replacer cmds))
> (ly:input-warning (*location*) "No volta text was replaced."
>
>#{ \context Score \applyContext #proc #})
>
> test = {
>\time 3/4
>\repeat volta 3
>{
> a'4 b' c' |
> \changeVoltaText "dud"
> #(ly:expect-warning "No volta text was replaced.")
> b'4 c' d' |
>}
>\alternative {
> {
>\changeVoltaText "1., 3."
>e'4 f' g' |
> }
> {
> d'4 c' b' |
> }
> {
>\changeVoltaText \markup \with-color #red "4."
>g'4 a' b' |
> }
>}
>c'1
> }
>
> \score {
>\test
> }
>
>
>
>
> -- Aaron Hill
>
Thanks for this modification, Aaron Hill.
Ralph
--
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Changing volta number text
On Fri, May 14, 2021 at 5:13 PM Aaron Hill wrote:
> On 2021-05-14 2:47 pm, Ralph Palmer wrote:
> > I *did* find a thread in the archive :
> > change of volta number
> > which has gotten me close, but has an extra end-repeat before the first
> > volta ending bracket. I'm also not sure the format is the most recent.
>
> How about this?
>
>
> \version "2.22.0"
> \include "english.ly"
>
> changeVoltaText =
> #(define-music-function
>(text) (markup?)
>(define (is-volta-text? cmd)
> (and (pair? cmd) (eq? 'volta (car cmd)) (markup? (cadr cmd
>(define (replace-volta-text cmd)
> (if (is-volta-text? cmd) `(volta ,text) cmd))
>(define (proc ctxt)
> (let ((cmds (ly:context-property ctxt 'repeatCommands)))
> (set! cmds (map replace-volta-text cmds))
> (ly:context-set-property! ctxt 'repeatCommands cmds)))
>#{ \context Score \applyContext #proc #} )
>
> test = {
>\time 3/4
>\repeat volta 3
>{
> a'4 b' c' |
> b'4 c' d' |
>}
>\alternative {
> {
>\changeVoltaText "1., 3."
>e'4 f' g' |
> }
> {
>d'4 c' b' |
> }
> {
>\changeVoltaText \markup \with-color #red "4."
>g'4 a' b' |
> }
>}
>c'1
> }
>
> \score {
>\test
> }
>
>
> NOTE: I'm using \markup in the final alternative just to demonstrate
> that it works.
>
>
> -- Aaron Hill
>
Excellent! Thank you, Aaron. I wish I could understand what your function
does - how it works.
Would it make sense to add this to either the Lilypond Snippet Repository
or the documentation or both?
All the best,
Ralph
--
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Changing volta number text
Greetings -
I appreciate the help this list has been over many years.
I've gone slightly crazy on a couple of occasions, trying to figure out how
to change a volta number, either to a different number(s) or to text.
It looked like a snippet in the LSR :
Volta text markup using repeatCommands [0.10714]
was going to help, but it just confused me more.
I *did* find a thread in the archive :
change of volta number
which has gotten me close, but has an extra end-repeat before the first
volta ending bracket. I'm also not sure the format is the most recent.
I think it would be helpful to either have a snippet that shows how to
change a "normal" volta number setup (i.e., change the numbers and/or add
text), or to add something to the documentation.
Here's the best I could come up with. I'd appreciate some help getting rid
of that initial repeat sign.
%%
\version "2.22.0"
\include "english.ly"
test = {
\time 3/4
\repeat volta 3
{
a'4 b' c' |
b'4 c' d' |
}
\alternative {
{
\set Score.repeatCommands = #'(end-repeat (volta "1., 3." ))
e'4 f' g' |
}
{
d'4 c' b' |
}
{
\set Score.repeatCommands = #'(end-repeat (volta "4."))
g'4 a' b' |
}
}
c'1
}
\score {
\test
}
%%%%%%%
Thanks for your help,
Ralph
--
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Documentation - issue #318 ; 1.4.2. Short repeats / Tremolos
Greetings - Darek Cidlinský has noticed the issue with whole note (two note) tremolo slashes not angling between the two whole notes. This has been accepted as issue #318. I suggest that a Known Issues and Warnings section be added to : 1.4.2. Short repeats Tremolos addressing the issue. Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in german documentation
On Fri, Jan 20, 2017 at 2:55 AM, Johannes Roeßler <j...@joei.de> wrote: > Hi, > > not sure, if I'm right on this list for this issue - if not, pls point me > where to go :) > > on http://lilypond.org/doc/v2.19/Documentation/notation/ > typesetting-mensural-music > the example for "Mensuraler F-Schlüssel im Petrucci-Stil" is not f-key but > c-key... > > Joei Thanks, Joei - I am forwarding your message to the LilyPond Bug List - bug-lilypond@gnu.org . Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
#4975 [Windows] Grace notes cause staff to protrude into the margin
Greetings -
I'm running LY 2.19.40 under Windows 7 SP1.
I ran into a situation that appears to be related to #4975.
Here's an .ly file that's about as small as I can get it:
Begin Snippet %
\version "2.19.40"
\include "english.ly"
tune =
\relative c'' {
\clef treble
\key a \minor
\time 6/8
e8 a a a4
\key a \major
e8 |
\acciaccatura b'8
a8 gs a a, cs e |
}
\score {
\tune
}
%% End Snippet %
This produces the following error message in the Frescobaldi log :
%%% Begin Snippet %%%
Preprocessing graphical objects...
programming error: mis-predicted force, 108.120472 ~= 108.221141
continuing, cross fingers
programming error: mis-predicted force, 108.120472 ~= 108.221141
continuing, cross fingers
Finding the ideal number of pages...
%%% End Snippet %%%
Commenting out either the key change (to A major) *or* the acciaccatura
eliminates the programming error.
This is not a serious issue for me right now. I thought this particular
instance might help point someone in the right direction for the solution
to the more general problem.
Thank you all for your continuing support, help, and understanding,
Ralph
--
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing of single beat "percent" repeats
> > > Not sure I'd agree, but it's already configureable: > > \override DoubleRepeatSlash.slash-negative-kern = #1.4 > %%default is 1.6 > > Cheers, > Harm > Thanks, Harm, Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
"Percent" repeats for mixed value beats with 32-notes
Greetings -
The Putney (VT) Community Orchestra, under Cailin Mason, recently performed
the Overture to Phedre by Massenet. In the viola part, there is a use of
percent repeats that makes sense but is not supported by LilyPond and is
not directly covered by either Gould ("Behind Bars:") or Read ("Music
Notation"). My stand partner, James Bergin, helped me figure out the
rationale behind the notation.
I no longer have access to the viola part, but here is the relevant section
from the score :
[image: Inline image 2]
The percent repeat used in the viola part looked like the repeats in the
following section in the documentation.
LilyPond — Notation Reference v2.19.34 (development-branch).
<http://www.lilypond.org/doc/v2.19/Documentation/notation/index>
1.4 Repeats
<http://www.lilypond.org/doc/v2.19/Documentation/notation/repeats>
1.4.2 Short repeats
<http://www.lilypond.org/doc/v2.19/Documentation/notation/short-repeats>
- Percent repeats
<http://www.lilypond.org/doc/v2.19/Documentation/notation/short-repeats#percent-repeats>
"Patterns that are shorter than one measure but contain mixed durations use
a double-percent symbol."
[image: Inline image 3]
except that the percent repeat signs had three slanting lines. Read says,
"Beats consisting of mixed values are abbreviated by using double slashes
accompanied by two dots:" and then shows repeat signs like the above
repeats (with a larger gap between signs), repeating a single beat
consisting of an eighth note and two sixteenth notes. James pointed out
that the repeat signs in The Overture to Phedre made sense if you took into
consideration the facts that : 1) the repeats were of single beats; 2) the
beats consisted of mixed values; and 3) the shortest duration was a
thirty-second note (having three flags or beams).
I would like to suggest that we consider adding (at least) the capability
of producing percent repeat signs with three bars. (I shall also suggest
wider, more legible spacing between percent repeat signs as the default,
but I shall do that in a separate email, to keep the threads separate.)
Thanks to all of you for your help, encouragement, and support!
I hope you have a Happy New Year,
Ralph
--
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
New issue submission process?
Greetings - Is there a new official submission process and / or location (web site)? If so, could someone please let me (us?) know? If a new site is on the horizon, but not yet here, is there a projected timeline? Does anyone besides myself need some explanation / explication? I appreciate your time and attention, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Apparent bug: Bracketed TupletNumber affected by Slur
On Thu, Aug 27, 2015 at 7:10 PM, Ralph Palmer palmer.r.vio...@gmail.com
wrote:
-- Forwarded message --
From: Daniel Rosen drose...@gmail.com
Date: Thu, Aug 27, 2015 at 5:24 PM
Subject: Apparent bug: Bracketed TupletNumber affected by Slur
To: lilypond-user Mailing List (lilypond-u...@gnu.org)
lilypond-u...@gnu.org
The following code produces the attached output, with the TupletNumber way
down inside the Slur even though there is no apparent reason for the
avoid-slur property to matter at all-in other words, this code should
produce the same output as if the \override were commented out. (The bug
appears to manifest only when the Slur begins on the first note of the
tuplet.)
Is this a bug? I can't seem to find anything like it in the bugs list
archives.
\version 2.19.25
\relative c'' {
\tupletUp
\override TupletNumber.avoid-slur = #'outside
\tuplet 3/2 { b8( b b) }
}
DR
___
lilypond-user mailing list
lilypond-u...@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Thanks for the report, Daniel Rosen. I'm forwarding this to the LilyPond
Bug list.
Ralph
My apologies to all - I should have copied Daniel Rosen and the LilyPond
mailing list.
Ralph
--
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Fwd: Apparent bug: Bracketed TupletNumber affected by Slur
-- Forwarded message --
From: Daniel Rosen drose...@gmail.com
Date: Thu, Aug 27, 2015 at 5:24 PM
Subject: Apparent bug: Bracketed TupletNumber affected by Slur
To: lilypond-user Mailing List (lilypond-u...@gnu.org)
lilypond-u...@gnu.org
The following code produces the attached output, with the TupletNumber way
down inside the Slur even though there is no apparent reason for the
avoid-slur property to matter at all-in other words, this code should
produce the same output as if the \override were commented out. (The bug
appears to manifest only when the Slur begins on the first note of the
tuplet.)
Is this a bug? I can't seem to find anything like it in the bugs list
archives.
\version 2.19.25
\relative c'' {
\tupletUp
\override TupletNumber.avoid-slur = #'outside
\tuplet 3/2 { b8( b b) }
}
DR
___
lilypond-user mailing list
lilypond-u...@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Thanks for the report, Daniel Rosen. I'm forwarding this to the LilyPond
Bug list.
Ralph
--
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Out of town, out of contact
Greetings - I will be out of town, and pretty much out of internet capability, for the next three Fridays. In other words, I shall not be able to cover August 28, September 4, or September 11. I apologize for any inconvenience this may cause. In gratitude for such a wonderful program and community, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Minor glitch in documentation of destination of Windows installation
On Thu, Aug 20, 2015 at 8:59 AM, Michael Gerdau m...@qata.de wrote: Dear bug squad, in Documentation/web/download.texi, line 486 it reads LilyPond will be installed under C:\Program Files on Windows. Since most current Windows Versions are 64bit this probably should read C:\Program Files (x86) Thanks, Michael Gerdau. This has been submitted as issue 4570 : https://code.google.com/p/lilypond/issues/detail?id=4570 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Move?
On Fri, Jul 10, 2015 at 7:59 AM, Federico Bruni f...@inventati.org wrote: Il giorno ven 10 lug 2015 alle 13:56, Ralph Palmer ralphbugl...@gmail.com ha scritto: What is the current status of the move away from Google Code? Do I have to learn a new system for reviewing emails and submitting issues? If so, I would like to get started as soon as possible. Hi Ralph I'm deploying Allura for the first time, so I have no idea how long it will take. Hopefully I'll have some time to work on it in the coming days. Anyway, I don't think that you will have much to learn, except for the different interface. Thanks for the update, Federico. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Small typo in german version of Notationsreferenz, header 2.9.3
On Thu, Jul 9, 2015 at 3:03 AM, Michael Gerdau m...@qata.de wrote: Hi Lilypond documentation team, in the german version of the Notationsreferenz, Headline 2.9.3 reads 2.9.3 Mesurale Musik setzen and it should be 2.9.3 Mensurale Musik setzen (an n is missing in Mensurale) The URL is http://www.lilypond.org/doc/v2.19/Documentation/notation/typesetting-mensural-music Best wishes, Michael Greetings, Michael, documentation team, and LilyPonders - Thanks for the email, Michael. I'm not sure if the bug list is the correct place to submit this, but I do not know of any list specific to documentation. This has been submitted as Issue 4490 : https://code.google.com/p/lilypond/issues/detail?id=4490 Best regards, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: inconspicuous ties
%% This tie is nearly invisible before the line break.
\score {{ r2 f'8 f' f' f'~ \break | f'2 r }}
I believe that this is issue 14?
https://code.google.com/p/lilypond/issues/detail?id=14
Not exactly. My complaint is not that the tie is too short, but that it
is too close to a staff line. The examples in that ticket focus on
intra-chord ties, but my example focuses on a line break.
I found an even simpler example:
\version 2.19.22
{ f' \laissezVibrer }
Gould p. 73 has an l.v. tie on a note in the same staff position. I think
it is clearer than the LilyPond output because the tips to not touch the
staff line.
—
Dan
Greetings, Dan. Thanks for the email. This has been submitted as Issue 4489
: https://code.google.com/p/lilypond/issues/detail?id=4489
All the best,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Move?
Greetings - What is the current status of the move away from Google Code? Do I have to learn a new system for reviewing emails and submitting issues? If so, I would like to get started as soon as possible. Once again : I'm amazed by and grateful for such a wonderful piece of software! Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement: expanded Woodwind diagrams
On Tue, Jun 30, 2015 at 4:20 PM, N. Andrew Walsh n.andrew.wa...@gmail.com wrote: The fingering diagrams for woodwinds are excellent. I'd like to request that they be expanded/improved, with several likely candidates: Greetings, Andrew - This has been submitted as Issue 4477 : https://code.google.com/p/lilypond/issues/detail?id=4477 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autochange looks ahead by only one rest
On Sun, Jun 28, 2015 at 8:57 AM, Dan Eble d...@faithful.be wrote: The Notation Reference says that \autochange looks ahead skipping over rests to switch in advance” and provides an example with a single rest. When there are multiple rests, it doesn’t move them all, which seems like a bug based on the NR. I’ve prepared a patch to change this, but I haven’t created a ticket because I am not certain that it is a bug. I’ve never used autochange and have no plans to use it; what do others think? https://codereview.appspot.com/247370043/ See auto-change.ly for sample input. Greetings, Dan - I haven't used \autochange, either, but it sounds like a bug to me. This has been submitted as issue 4476 : https://code.google.com/p/lilypond/issues/detail?id=4476 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: dodecaphonic-no-repeat and grace notes
On Sun, Jun 7, 2015 at 8:39 AM, Simon Albrecht simon.albre...@mail.de wrote: Forwarding to the bug-list. Yours, Simon Am 07.06.2015 um 02:52 schrieb Gilberto Agostinho: Hi all, I found a little problem with the \accidentalStyle dodecaphonic-no-repeat. When there is a grace note between two identical pitches, the second one does not receive an accidental as it's suppose to: Thanks, Simon and Gilberto. This has been submitted as Issue 4458 : https://code.google.com/p/lilypond/issues/detail?id=4458 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \tempo collision with cross staff beam
On Mon, Jun 1, 2015 at 9:03 AM, Urs Liska u...@openlilylib.org wrote: Hi bug squad, I ran into a collision bug. With a cross-staff beam present \tempo doesn't take any objects above the staff into account. If you comment out the beam in the following example the \tempo is correctly shifted upwards to accomodate the dynamic. Result is identical with 2.18.2 and 2.19.22. This may be related to 3778, but strangely so: Hi, Urs - Thanks for the report. I've submitted this as Issue 4332 : https://code.google.com/p/lilypond/issues/detail?id=4432 and asked for confirmation from the developers as to whether this is the same as, or contained in, Issue 3778. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Inconsistent interpretation of intervals in chord mode
On Fri, Jun 5, 2015 at 4:51 AM, pls p.l.schm...@gmx.de wrote: Hey all, in chord mode the basic seventh step added to a tonic is the flattened seventh (e.g. c:1.7). Diminished sevenths and major sevenths can be achieved by suffixing a '-' or '+' to the number (e.g. c:1.7- or c:1.7+). But this interpretation changes when the notes extend beyond the range of one octave. c:1.14 is now interpreted as a major seventh, c:1.14+ and c:1.14- are now displayed as an augmented major seventh and a flattened seventh, respectively (see attachment). Currently it's not possible at all to display a diminished seventh one octave higher. So this looks like a bug to me. Thanks for the report, Patrick. This has been submitted as Issue 4433 : https://code.google.com/p/lilypond/issues/detail?id=4433 All the best, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Squad
On Wed, Jun 3, 2015 at 3:47 PM, Simon Albrecht simon.albre...@mail.de wrote: Hello Bug squad, is the list in http://lilypond.org/doc/v2.19/Documentation/contributor/bug-squad-checklists anywhere near up-to-date? It seems we don’t have a really prompt squad at hand, and I should be able to take over one or two days, except for Monday and Thursday. Yours, Simon Greetings, Simon et al. - I'm still on Friday, although I confess I miss a week occasionally. I'll be getting to today's (June 5) list in an hour or two. All the best, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly doesn't handle nested tuplets
On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska u...@openlilylib.org wrote: When dealing with export of nested tuplets to MusicXML ( https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how nested tuplets are rendered after importing into lilypond. Urs I can't tell from the LilyPond documentation whether MusicXML - either import, export, or both - is explicitly supported by LilyPond. Before I submit this as an issue, can someone please confirm for me that LilyPond does support MusicXML? I appreciate your time and help, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly doesn't handle nested tuplets
On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska u...@openlilylib.org wrote: When dealing with export of nested tuplets to MusicXML ( https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how nested tuplets are rendered after importing into lilypond. Urs Thanks for the report, Urs. (And thanks for the clarification, as well!) This has been submitted as Issue 4434 : https://code.google.com/p/lilypond/issues/detail?id=4434 All the best, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Accessibility of score/bookpart header variables in headerMarkup
On Wed, May 20, 2015 at 12:58 PM, Leah Velleman leah.velle...@gmail.com
wrote:
The manual
(http://www.lilypond.org/doc/v2.19/Documentation/notation/
creating-titles-headers-and-footers#titles-explained) says
that evenHeaderMarkup and other header/footer variables...
can only access text fields from top-level \header blocks
(which apply to all scores in the book)
In fact, this is not true. they can also access text fields
from \header blocks at levels as low as bookpart, as the
following MWE shows:
\version 2.19
\paper {
oddHeaderMarkup = \markup { \fromproperty #'header:title }
evenHeaderMarkup = \markup { \fromproperty #'header:title }
scoreTitleMarkup = \markup { }
bookTitleMarkup = \markup { }
}
\book {
\bookpart {
\header { title = foo bar baz }
\score {
\new Staff { c d e f g a b c }
}
}
}
Greetings, Leah - This has been submitted as Issue 4412 :
https://code.google.com/p/lilypond/issues/detail?id=4412
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Accessibility of score/bookpart header variables in headerMarkup
On Wed, May 20, 2015 at 12:58 PM, Leah Velleman leah.velle...@gmail.com wrote: It would sometimes be useful to be able to access fields from score-level header blocks as well as from top-, book- and bookpart-level ones. (The use case I have in mind is printing PIECE TITLE (cont'd) at the top of the second and subsequent pages of a piece. There are probably others.) The restriction to bookpart-level and higher header blocks seems arbitrary, and I wonder if it could be removed. Greetings, Leah - This has been submitted as Issue 4413 - https://code.google.com/p/lilypond/issues/detail?id=4413 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Incorrect interaction of stemLeft/RightBeamCount and Score.skipTypesetting
On Fri, May 1, 2015 at 10:44 PM, Rob Tuley rob.tu...@btinternet.com wrote:
I'm not top posting.
Wrong output: the \set stemRightBeamCount and \set stemLeftBeamCount
are incorrectly applied to the first note AFTER
\set Score.skipTypesetting = ##f.
\version 2.18.2
{ $\set Score.skipTypesetting = ##t
c'16 \set stemRightBeamCount = #1 c' \set stemLeftBeamCount = #1 c' c'
\set Score.skipTypesetting = ##f
c' c' c' c'
}
Has anyone replied privately to Rob Tuley on this issue? I could not get
the snippet to compile in 2.18.2 until I commented out the
$\set Score.skipTypesetting = ##t
Once I did that, the behavior of the rest of the snippet was as I would
expect. However, I do not understand why Score.skipTypsetting is included
at all.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Completion_heads_engraver and dotted breve
On Mon, Apr 27, 2015 at 4:05 AM, Simon Albrecht simon.albre...@mail.de wrote: Hello, Completion_heads_engraver doesn’t use dotted breve notes for its output, where smaller note values work as expected. Thanks, Simon Thanks, Simon. Submitted as Issue 4362 : https://code.google.com/p/lilypond/issues/detail?id=4362 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: figured bass on grace note
On Tue, Apr 28, 2015 at 10:58 PM, Yuan Ye yuanyel...@openmailbox.org wrote: I believe there is a bug when writing figured bass on grace note. The figure before the grace note is repeated on the grace note. Here is a tiny example: The second figure should be 5 but turns out 6 5. Thanks, Yuan Ye. This has been submitted as Issue 4363 : https://code.google.com/p/lilypond/issues/detail?id=4363 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Roman Numeral placement
On Tue, Apr 21, 2015 at 6:27 PM, Carl Sorensen c_soren...@byu.edu wrote: On 4/21/15 10:34 AM, SonusProj . sonusproject...@gmail.com wrote: I want to add below the chord, treble clef, the associated Roman numeral description of each chord. I.E. on the C Major I would have I, the Dm7 would have ii7 with the 7 in superscript, the Em7 would have iii7 with the 7 in superscript, etc. I see several avenues for this but I don't see an avenue where I can write the code once and use many times. I want the Roman numerals to appear for all keys and don't want an overly clutter code. It seems that what is really wanted here (although not currently available in LilyPond as far as I know) is a scale-degree chord namer. This would be a reasonable feature request. I'll copy to bug-lilypond so the bug squad can do their magic. Thanks, Carl Thanks, Carl and SonusProj. This has been submitted as Issue 4354 : https://code.google.com/p/lilypond/issues/detail?id=4354 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement: automatically translate tagline
On Wed, Mar 25, 2015 at 9:58 AM, Simon Albrecht simon.albre...@mail.de wrote: please open a tracker issue for this thread. I’m going to make another essay at coding something sensible. Done, Simon : Issue 4337 - https://code.google.com/p/lilypond/issues/detail?id=4337 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement: support modern-style ties
On Sun, Mar 22, 2015 at 5:37 PM, Simon Albrecht simon.albre...@mail.de wrote: I suggest adding a 'style property with the following possible values: 'full-length (default) 'modern-single (or 'modern) 'modern-double Greetings, Simon Albrecht - Thanks for the request. It has been submitted as Issue 4336 : https://code.google.com/p/lilypond/issues/detail?id=4336 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond crash in special case
On Tue, Mar 31, 2015 at 7:29 PM, Thomas Morley thomasmorle...@gmail.com wrote: 2015-03-31 16:54 GMT+02:00 Simon Albrecht simon.albre...@mail.de: Am 31.03.2015 um 14:59 schrieb Phil Holmes: Leo Naab leo.n...@gmx.de wrote in message news:loom.20150331t133343-...@post.gmane.org... I have a special lilypond file with let's lilypond.exe crash. The file works fine with version 2.19.15, but not with 2.19.17. The crash has do to with a \new Lyric line. \new Lyric in \context Staff didn't work, but if the \new Lyric comes behind the \context Staff all is fine. Submitted as Issue 4339. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Octavecheck?
On Wed, Mar 25, 2015 at 3:04 PM, Trevor Daniels t.dani...@treda.co.uk wrote: Noeck wrote Wednesday, March 25, 2015 6:48 PM Here is a guess what happens (even if that contradicts the docs): The following pitches are perhaps not relative to the octave check but to the previous pitch corrected by the octave check. That would be my explanation too. This would explain it, but the docs would have to be corrected. Yes, it's a doc issue. But is it really useful in this form? Does anyone use it? Greetings, Trevor, Noeck, et al. - Submitted as Issue 4338 : https://code.google.com/p/lilypond/issues/detail?id=4338 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: markLengthOn fails, if MetronomeMark/RehearsalMark-direction is DOWN
On Thu, Mar 12, 2015 at 10:12 PM, Thomas Morley thomasmorle...@gmail.com wrote: \markLengthOn returns wrong output for MetronomeMark and RehearsalMark, while their direction is DOWN. Thanks for the report, Harm. Submitted as Issue 4320 : https://code.google.com/p/lilypond/issues/detail?id=4320 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NullVoice and Ambitus crash (regression?)
On Wed, Feb 25, 2015 at 3:29 PM, Simon Albrecht simon.albre...@mail.de wrote: if in Lily 2.19.15 NullVoice is \consisted with the Ambitus_engraver, there are (for one NullVoice) three instances of programming error: tried to get a translation for something that is no child of mine which cause the program to abort. This used to work in v2.19.8. Minimal example attached. In case you ask why I’d want this: I have two choir parts assembled in one staff using \partcombine. Two NullVoices are required for separate lyrics, and for separate ambitus. Thanks for the report, Simon. This has been submitted as Issue 4302 : https://code.google.com/p/lilypond/issues/detail?id=4302 Cheers, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hairpin crash
On Wed, Feb 18, 2015 at 4:46 AM, Simon Albrecht simon.albre...@mail.de wrote: The hairpins collide, if and only if -- there is a barline in \n (comment to test) -- and there is a half note or rest or multi-measure-rest in the other part. Somewhat obscure and difficult to isolate, but easy to work around. Thanks, Simon Albrecht. This has been submitted as Issue 4301 : https://code.google.com/p/lilypond/issues/detail?id=4301 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Apologies for Issues 4279 and 4280
Greetings - I didn't realize that Google was using my private email address, so Issue 4279 was not submitted correctly (no issue label), and 4280 was a complete mistake. I do not know how to delete an issue, so please, someone either delete or recycle Issue 4280 and give a correct label to Issue 4279. I will take care to avoid this situation in the future. I appreciate your time and attention, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: faulty interaction of line-width and minimum-length in spanners
On Tue, Feb 3, 2015 at 1:50 PM, David Nalesnik david.nales...@gmail.com
wrote:
In the following snippet, the music runs right off the page. Clearly, the
setting of line-width is not respected. Probably, it should be
minimum-width that is ignored or adjusted along with an error being thrown.
%%%
\paper {
line-width = 50\mm
}
{
\override Tie.minimum-length = #40
c''2 ~ c'' ~ \break
c''2 ~ c''
}
%%%
David
Thanks, David. Submitted as Issue 4279 :
https://code.google.com/p/lilypond/issues/detail?id=4279
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Build issue in Fedora due to font changes
On Wed, Jan 21, 2015 at 9:37 AM, Jon Ciesla limburg...@gmail.com wrote: FYI, Fedora has reverted the urw-fonts change, but this is still something to consider fixing, as the change will need to be made eventually, and on multiple distributions. Jon and Werner and List - Just so this doesn't get lost in the shuffle, I've submitted it as Issue 4272 : https://code.google.com/p/lilypond/issues/detail?id=4272 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: wish: ly:cheapest-breaking (or whatever name)
On Mon, Jan 19, 2015 at 9:33 AM, Urs Liska u...@openlilylib.org wrote: Hi list, following up on a thread that I started some time ago ( http://lists.gnu.org/archive/html/lilypond-devel/2014-11/msg00139.html) I'd like to draw the conclusions from that and ask for an additional breaking algorithm. Hi, Urs and List - At the risk of creating noise, but hoping to help keep it from getting lost, I've submitted this as a feature request : Issue 4271 https://code.google.com/p/lilypond/issues/detail?id=4271. Please let me know if this was impertinent or unnecessary. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Dynamic positioning in dynamic context
On Sun, Jan 4, 2015 at 4:59 AM, Helge Kruse helge.kr...@gmx.net wrote:
Hello,
I have an improvement request.
The dynamic context has a lot of advantages. Most important it makes a
uniform vertical position of all dynamics in a line. Unfortunately it
doesn't behave with the horizontal spacing.
The following example starts with a spacer rest measure. The \p in the
second measure is placed as expected. But if the dynamic has more width
it collides with the bar. This doesn't happen when I add the dynamic to
the upper staff in the third measure. Here you can find a small space
between the bar and the first note (d).
Can this be improved so that the width of objects in the dynamic context
control the spacing in the staff context?
\version 2.19.15
\language deutsch
global = { \time 3/4 }
upper = \relative c' {
s2.
d4\p\( e \acciaccatura{g8} f4-\)
d4\( e \acciaccatura{g8} f4-\)
d4\ppp\\( e \acciaccatura{g8} f4-\)
s2.\! s
}
dynamic = {
s2.
s2.\p
s2.\ppp\
s2.\! s2.
}
lower = { s2. s s s }
\new PianoStaff
\new Staff = Staff_pfUpper \global \upper
\new Dynamics = Dynamics_pf \global \dynamic
\new Staff = Staff_pfLower \global \lower
Greetings, Helge Kruse - This has been submitted as issue 4253 :
https://code.google.com/p/lilypond/issues/detail?id=4253
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Typo in NR example (vocal music)
On Wed, Jan 7, 2015 at 4:50 AM, Urs Liska u...@openlilylib.org wrote: Hi all, on http://lilypond.org/doc/v2.19/Documentation/notation/common- notation-for-vocal-music.html there's a typo in the example about special characters (with the text Schad' um das schöne grüne Band). The sixth note should read es' instead of e'. I'd fix that myself but I have problems accessing the Git repository right now. Therefore I write this email so it won't be forgotten. Urs Thanks, Urs. Submitted as issue 4254 : https://code.google.com/p/lilypond/issues/detail?id=4254 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Melody engraver enhancement
On Sun, Dec 28, 2014 at 10:25 AM, Simon Albrecht simon.albre...@mail.de wrote: Hello everybody, in the attached example, two tied notes (of the same pitch) in different bars have their stems placed in different directions by the melody engraver. This is very confusing, so the engraver should take ties between notes of the same pitch (that is, as opposed to bis~ c for example) into account (and use \downStem in case of doubt...). Yours sincerely, Simon I do not have a copy of Gould, and my copy of Read is not accessible, so I can't check this, but it does seem as though it would help readability for musicians. It has been submitted as an enhancement request : Issue 4240 : https://code.google.com/p/lilypond/issues/detail?id=4240 Thanks, Simon, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: footnotes in markup attached to notes not working
On Sat, Dec 6, 2014 at 10:57 PM, Dan McMahill d...@mcmahill.net wrote:
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 {
\hornPartA
\layout { }
\midi { }
}
Greetings, Dan -
Please check out 3.2.3 Creating footnotes
http://lilypond.org/doc/v2.18/Documentation/notation/creating-footnotes in
the Notation Reference.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Cross-staff beam problems (collisions ugly slope)
On Tue, Nov 18, 2014 at 7:17 PM, Marcus Macauley marcus.macau...@gmail.com wrote: \version 2.18.2 The example above is my attempt at a tiny illustration of three simultaneous problems with a cross-staff beam: collisions (of beam with notes or accidentals); ugly slopes; and ugly horizontal spacing (stem spacing overcorrection). I checked the Lilypond Google Project Bug Tracker before making this, and the most similar issues I could find were 1324 and 1702, but I don't believe this is fully redundant. Greetings, Marcus Macauley - I apologize for misspelling your last name in the submission. This has been submitted as Issue 4202 ; https://code.google.com/p/lilypond/issues/detail?id=4202 Cheers, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bad slur
On Sat, Nov 8, 2014 at 7:18 AM, Federico Bruni fedel...@gmail.com wrote:
In the attached image the slur starts in a point too far away from the
note head. Is it a bug?
I've searched the tracker but there are so many issues about slurs that
I'm not sure if this problem is known.
\version 2.19.15
\relative c'' {
\time 2/4
g'16 d bes g( fis g) bes d |
}
Thanks, Federico. This has been entered as Issue 4194 :
https://code.google.com/p/lilypond/issues/detail?id=4194
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: ly:page-turn-breaking also adds a page turn to very short sheet music
On Wed, Oct 8, 2014 at 5:12 AM, ArnoldTheresius arnold.we...@siemens.com
wrote:
I'm not top posting.
Compiling with 2.18.2 on Win7/64 (another user tested it on Mac) I get two
pages,
the first page with the first score block (one line of sheet music),
and the second score block (two lines of sheet music) on the second page.
With 2.18.0 on Win7/64 (and 2.16.2 on Mac OX X 10.4.11) the result
was as expected on one page only. It easily fits on one page.
Example:
\version 2.18.0
\paper {
page-breaking = #ly:page-turn-breaking
}
\header{
title = odd-pageturnbreaking.ly
}
I = {
\repeat unfold 16 g'4
\bar ||
}
II = {
\repeat unfold 52 g'4
\bar ||
}
\score {
\new Staff {
\I
}
}
\score {
\new Staff {
\II
}
}
%% END of example
ArnoldTheresius
Thanks, ArnoldTheresius. Submitted as Issue 4166 :
https://code.google.com/p/lilypond/issues/detail?id=4166
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bad tie placement
On Wed, Oct 15, 2014 at 4:41 PM, Abraham Lee tisimst.lilyp...@gmail.com
wrote:
My LP Friends,
While scoring a song, I noticed a rather poor tie placement in a chord.
Here's the code:
\version 2.18.2
music = \relative c'{
\key aes \major
\time 2/2
\numericTimeSignature
\partial 2 g'4 ( f ) |
c ees4 ees c ees bes ees |
bes'2. ees,4 |
des ees-\tweak color #red ~ aes~1_( |
c ees aes2. ) \bar |.
}
\paper {
paper-width = 7\in
ragged-last = ##f
indent = 0
}
\header {
tagline = ##f
}
\markup \voiceOne, ragged-last=##f, bad tie placement
\score {
{ \voiceOne \music }
}
\markup \voiceOne, ragged-last=##t, normal voiced tie placement
\score {
\layout {
ragged-last = ##t
}
{ \voiceOne \music }
}
\markup (default voice), ragged-last=##f, normal non-voiced tie placement
\score {
{ \music }
}
See the attached file for a picture of the above issue (bad tie indicated
in red).
1. In the first system, and in my song, all the notes need to be
\voiceOne. The default placement of the ties is up, but the placement is
horrid on the ees in the last two measures. If I manually flip it down,
then it looks great (which I've gone with). This appears to be an issue
with the length of the system because ... (see #2).
2. When I shorten the system (i.e., ragged-last = ##f), then the default,
voiced tie placement is as I would expect it.
3. When I make the system be the same length as the original, and either
manually switch the direction or remove the explicit \voiceOne, then the
downward tie also places perfectly.
4. (Not shown) If you extend the paper-width to be something like 10\in,
then the default, voiced tie is once again placed correctly (but not at
9.99\in).
I guess all I'm saying is that from paper-width of 5.8\in to 9.99\in, and
forcing everything into \voiceOne, the ties are placed incorrectly than
outside that range. Any ideas what's causing it?
Regards,
Abraham
Thanks, Abraham. Submitted as Issue 4167 :
https://code.google.com/p/lilypond/issues/detail?id=4167
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Cross staff stems don’t work with shifted notes
On Mon, Sep 29, 2014 at 12:00 PM, Malte Meyn lilyp...@maltemeyn.de wrote:
I'm not top posting.
The following won’t shift the C (or the A) horizontally and connect the
stems of G and C.
\version 2.19.13
\new PianoStaff \with {
\consists #Span_stem_engraver
}
a'
\\
\crossStaff g' %change this to f' and it will work
c''
Greetings - this has been submitted as Issue 4150 :
https://code.google.com/p/lilypond/issues/detail?id=4150
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: implicitTimeSignatureVisibility
On Mon, Sep 29, 2014 at 8:32 PM, Dan Eble nine.fierce.ball...@gmail.com
wrote:
I'm not top posting.
% I'm not sure if this is a defect in functionality, nomenclature,
% documentation, or all three.
%
% It is not clear what is implicit about
% implicitTimeSignatureVisibility, since it has the same effect
% whether the time signature is omitted or specified.
%
% The notation reference says that implicitTimeSignatureVisibility
% is break visibility for the default time signature, yet it has the
% same effect whether the time signature is the default 4/4 or
% something else.
%
% What it does appear to do is control the visibility of the first
% time signature.
\version 2.19.14
\score {
\relative { c'1^Default, Implicit (Visible) }
}
\score {
\relative {
\set Score.implicitTimeSignatureVisibility = #all-invisible
c'1^Default, Implicit
}
}
\score {
\relative {
\set Score.implicitTimeSignatureVisibility = #all-invisible
\time 4/4 c'1^Default, Explicit
}
}
\score {
\relative {
\set Score.implicitTimeSignatureVisibility = #all-invisible
\time 3/4 c'2.^Non-default, Explicit
}
}
Greetings - this has been submitted as Issue 4151 :
https://code.google.com/p/lilypond/issues/detail?id=4151
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Notes with different pitches sharing a staff line are engraved strangely
On Sun, Aug 31, 2014 at 3:06 PM, Dan Eble d...@faithful.be wrote:
I'm not top posting.
% This example might be worth more than one ticket.
\version 2.18.0
\language english
upper = \relative { bs'4 }
lower = \relative { b'4 }
chord = \relative { bs' b4 }
% In this case, the output clearly represents something other than the
% input. The input doesn't make much sense in the kinds of music I'm
% familiar with, so I don't think there is a major problem with what
% Lilypond has done except that it should warn that it did not engrave
% what was requested.
\score {
\new Staff
\set Staff.instrumentName =
\dynamicUp \upper
\\
\dynamicDown \lower
}
% In this case, I'm not sure what the output represents, but unless
% Lilypond is already engraving the expected musical notation, it
% should warn.
\score {
\new Staff
\set Staff.instrumentName =
\chord
}
% The part combiner can choose either to put the two notes in separate
% voices or in the same voice. Is the current behavior the better
% choice in this case? Possibly not.
\score {
\new Staff
\set Staff.instrumentName = partcombine
\partcombine \upper \lower
}
% ... and the CAPTCHA is oddities. How appropriate. :-)
Greetings, Dan Eble. Thanks for the email. This has been submitted as Issue
4113. https://code.google.com/p/lilypond/issues/detail?id=4113
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Loose column does not have right side to attach to.
On Tue, Aug 26, 2014 at 9:29 PM, Dan Eble d...@faithful.be wrote:
I'm not top posting.
% programming error: Loose column does not have right side to attach to.
\version 2.18.0
\language english
music = \relative c' {
c4. c
}
bars = \relative f {
s2
\once \override Timing.BarLine.break-visibility = #end-of-line-visible
\bar .
}
\score {
\new Staff \music \bars
}
Thanks, Dan Eble. Submitted as issue 4084 :
https://code.google.com/p/lilypond/issues/detail?id=4084
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Back in town
Greetings, Bug Listers - I'm back in town, and ready to start working on the bug list again, if you want my help. I've been out of town (on the road) and out of touch. What days are available? If there's an open day and anyone wants to switch to it, I'm willing to consider it. Catch you all later, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Back in town
You've got it, Federico. I'll take Friday. Ralph On Mon, Aug 25, 2014 at 2:33 PM, Federico Bruni fedel...@gmail.com wrote: Il 25/ago/2014 17:16 James pkx1...@gmail.com ha scritto: Hello Ralph, http://lilypond.org/doc/v2.19/Documentation/contributor-big-page.html#bug-squad-checklists Take your pick. James I see that I've been removed from the list. I'm still in vacation but I'll be back next week. I'd like to pick tuesday ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Off Bug Squad temporarily
Greetings - I've been quiet recently. I apologize for having missed some Tuesdays. I will be semi-unavailable until the middle of August, so I'm afraid I'm going to have to stop doing Bug Squad duties until at least then. I apologize for any inconvenience, and I'll jump back in as soon as I can. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bad number formatting in svg path output
On Thu, Mar 6, 2014 at 1:50 PM, lpietsch lukas.piet...@freenet.de wrote: There may be a bug in scm/output-svg.scm, in the function that processes stencil expressions created with (ly:create-stencil '(path ...)). If a coordinate in the path expression happens to be the result of a Scheme computation that is a fractional rational number, it will be written into the SVG output literally as a Scheme fraction (e.g. 3/2). SVG does not understand this format. Test snippet: \once \override NoteHead.stencil = #(ly:make-stencil `(path 0.2 '(moveto 0 0 rlineto 0 ,(/ 3 2)) 'round 'round #f) '(-0.1 . 0.1)'(0 . 1.5)) c4 This stencil will not display in SVG output, though it does display fine in PS and PDF. A possible fix may be to change line 86 of /scm/output-svg.scm to force output as a decimal number. Change from: (cons (format #f ~S ~S (car lst) (- (cadr lst))) to: (cons (ly:format ~4f ~4f (car lst) (- (cadr lst))) Lukas Greetings, Lukas - Thanks for the email. This has been submitted as Issue 3880 : https://code.google.com/p/lilypond/issues/detail?id=3880 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: staccato overlaping on staff line
On Sat, Mar 8, 2014 at 4:50 PM, Karol Majewski karo...@wp.pl wrote:
\version 2.19.3
upper = {
\clef treble \time 2/4
\voiceOne a''8 \noBeam b' d'' g''8
}
lower = {
\clef bass \time 2/4
\override Beam.auto-knee-gap = ##f
\voiceTwo b8 -. \change Staff = upper d' e' g'8 -.
}
\score {
\new PianoStaff
\new Staff = upper \upper
\new Staff = lower \lower
}
Greetings, Karol Majewski - This has been submitted as Issue 3881 :
https://code.google.com/p/lilypond/issues/detail?id=3881
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: stencils with stroke-thickness set to zero
On Mon, Mar 10, 2014 at 8:11 AM, lpietsch lukas.piet...@freenet.de wrote:
There seems to be an inconsistency between the PS and the SVG backends in
the
treatment of path stencils. In PS, it seems to be impossible to create a
filled shape with no visible contour line, whereas in SVG this is possible.
If you create a stencil with the thickness parameter set to zero (via
make-path-stencil or via (ly:make-stencil ('path ...), the SVG backend
will do just that: no visible contour stroke, just a filled shape. The PS
backend will add a visible hairline around the stencil, giving it at least
one pixel in extra width. This may result in quite a visible difference
between the two results, at least in screen display and with small or thin
shapes.
Test snippet:
#(define teststencil (make-path-stencil
'(moveto 0 0 lineto 0 1 lineto 0.05 1 lineto 0.05 0 closepath)
0 1 1 #t))
\markup { \stencil #teststencil }
This will result in a markedly thicker line on screen in the PS output than
in the SVG output.
To bring the PS behaviour in line with the SVG behaviour (which I find more
intuitive and more logical), change the path function in scm/output-ps.scm
so as to omit the stroke command if the fill parameter is #t and the
thickness parameter is zero. Change l.286-294 from:
(ly:format
gsave currentpoint translate
~a setlinecap ~a setlinejoin ~a setlinewidth
~l gsave stroke grestore ~a grestore
cap-numeric
join-numeric
thickness
(convert-path-exps exps)
(if fill? fill
to:
(ly:format
gsave currentpoint translate
~a setlinecap ~a setlinejoin ~a setlinewidth
~l ~a ~a grestore
cap-numeric
join-numeric
thickness
(convert-path-exps exps)
(if (or (not fill?)( thickness 0)) gsave stroke grestore )
(if fill? fill
Greetings, Lukas - This has been submitted as Issue 3882 :
https://code.google.com/p/lilypond/issues/detail?id=3882
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Midi early start (2.19.2)
On Tue, Feb 11, 2014 at 8:40 PM, Jay Anderson horndud...@gmail.com wrote: Removing the Dynamic_performer causes rests at the start of a piece to be skipped causing misalignment with other voices. I've only tested this with 2.19.2 and 2.18.0. It works correctly in 2.18.0. Thanks, Jay Anderson - This has been submitted as Issue 3871 : https://code.google.com/p/lilypond/issues/detail?id=3871 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: programming error with \markup \vspace used in \header
On Thu, Jan 30, 2014 at 5:31 AM, Thomas Morley thomasmorle...@gmail.comwrote:
Hi,
the following code returns:
programming error: Improbable offset for stencil: -inf staff space
Setting to zero.
although the printed output seems to be correct.
\version 2.19.1
\header { title = \markup \vspace #10 }
\markup xy
I noticed the error with 2.17.97, 2.18.0 and 2.19.1
2.16.2 returned no error.
A stand alone \markup \vspace #10 throws no error.
Greetings, Harm -
Could you please give us a compilable minimal example?
Thanks,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: b:7 chord in predefined-guitar-fretboards.ly
On Sun, Dec 22, 2013 at 5:48 AM, Federico Bruni fedel...@gmail.com wrote:
I think that a user would expect to see the most commonly used chords, i.e.
the chords in first position (without barré).
Shouldn't the b:7 be written explicitly instead of deriving it from the
bes:7 shape?
\version 2.17.97
\storePredefinedDiagram #default-fret-table
\chordmode { b:7 }
#guitar-tuning
#x;2-2;1-1;2-3;o;2-4;
myChords = \chordmode {
b:7
}
\new ChordNames { \myChords }
\new FretBoards { \myChords }
Sorry this took so long, Federico. It's been entered as issue 3791 :
https://code.google.com/p/lilypond/issues/detail?id=3791
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: b:7 chord in predefined-guitar-fretboards.ly
On Sun, Dec 22, 2013 at 5:48 AM, Federico Bruni fedel...@gmail.com wrote:
I think that a user would expect to see the most commonly used chords, i.e.
the chords in first position (without barré).
Shouldn't the b:7 be written explicitly instead of deriving it from the
bes:7 shape?
\version 2.17.97
\storePredefinedDiagram #default-fret-table
\chordmode { b:7 }
#guitar-tuning
#x;2-2;1-1;2-3;o;2-4;
myChords = \chordmode {
b:7
}
\new ChordNames { \myChords }
\new FretBoards { \myChords }
Greetings, Federico. Are you asking for an enhancement?
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: website: why removing lilypond distro package?
On Mon, Dec 16, 2013 at 6:22 PM, Federico Bruni fedel...@gmail.com wrote: http://lilypond.org/website/unix.html Maybe we could change the sentence to: Generic Packages or Distribution-Specific Packages? Many distributions include LilyPond in their normal package system. These versions are easier to install and uninstall than the generic packages, but they may be older. If you wish to use our generic packages, please check that your editor of choice is using the correct version of lilypond. Read more on Hi, Federico. Thanks for the email. This has been submitted as Issue 3735 : https://code.google.com/p/lilypond/issues/detail?id=3735 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue labels
On Tue, Dec 3, 2013 at 4:54 PM, David Kastrup d...@gnu.org wrote: I think Ugly means bad decisions, usually based on insufficient detail in the algorithms. Defect means that things go different than intended by the programmer. There is some overlap, but if staves are not getting removed that should be or vice versa, that's Defect in my opinion. Thanks for your quick and clear response, David. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Percent repeat
On Sat, Nov 30, 2013 at 2:26 PM, Janek Warchoł janek.lilyp...@gmail.comwrote: Hi, 2013/11/30 Noeck noeck.marb...@gmx.de: Hi, is this a bug or is there some reason why this should be correct: If I use a percent repeat in a customly timed measure (5/4 instead of 4/4), the repeat symbol lacks the dots and is placed to the left of the bar. If I write something before the repeat (a time signature or only ), then the dots reappear and they are placed properly. looks like a bug to me. Forwarding to bug-lilypond. Thanks, Noeck and Janek - This has been entered as Issue 3703 : https://code.google.com/p/lilypond/issues/detail?id=3703colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue labels
Hi, everyone - I'm a little confused. I've been entering issues as Ugly which don't really seem to fit. Should they be Defects? What would constitute a defect in the core program? For example, would the ambitus problems recently reported be better classified as defects? I appreciate your time and attention, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: RehearsalMark breaks system's ref-point? (was: The ultimate slur shaping function)
On Mon, Nov 25, 2013 at 5:22 PM, Janek Warchoł janek.lilyp...@gmail.comwrote:
Hi all,
it seems that when there is a RehearsalMark, the reference point of a
system changes and the relative extents are calculated in an
unreasonable way.
Here's the background - i got a bug report about \shapeII:
2013/11/25 Ed Gordijn ed.klari...@gmail.com:
Hi Janek,
This [\shapeII] is a very nice function you have made. But I get
unexpected results
when I use a rehearsal mark.
Please see the included snippet.
I did some tests and here's what i got. I have a function (it's very
lame, i know) that does some bogus override of a slur's positions
property, and in the meantime it prints the relative Y-extent of
slur's left NoteColumn:
\version 2.17.96
foo =
#(define-music-function (parser location item)
(symbol-list-or-music?)
(define (quux grob)
(let* ((orig (ly:grob-original grob))
(bound (ly:spanner-bound grob LEFT))
(ref (ly:grob-system bound)))
;; print the extent of the left NoteColumn relative to the system:
(display (ly:grob-extent bound ref Y))
;; bogus value:
(cons 3 3)))
#{ \tweak positions #quux #item #})
\relative c'' {
\foo Slur
d1( c')
}
In this case it outputs (0.449994 . 1.550006) - as expected: the
extent of the d note, measured relative to middle staffline, is
roughly (0.45 . 1.55) staffspaces.
But when i add a rehearsal mark:
\relative c'' {
\foo Slur
d1( c')
\mark \default
}
the output is (-4.100012 . -3.0), as if the point against which the
extent is measured was on top of the higher note (instead of middle
staff line). Indeed, if i change the higher note to e
\relative c'' {
\foo Slur
d1( e')
\mark \default
}
the extent is further lowered by 1 ss: (-5.100012 . -4.0)
This behaviour seems extremely weird to me. Do you know anything about
this?
best,
Janek
Hi, Janek - I went ahead and submitted this as Issue 3677 :
https://code.google.com/p/lilypond/issues/detail?id=3677
Hope I wasn't out of line!
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Squad Roll Call
On Tue, Nov 12, 2013 at 12:58 PM, Colin Campbell c...@shaw.ca wrote: ** In the interests of getting the Bug Squad back on track, shall we take a roll call, with each member identifying themselves and stating for which day(s) they are responsible? It would also be useful to know whether or not there is a current meister. To facilitate reply: *=== Member DaysMeister? Monday Ralph PalmerTuesday Wednesday Thursday Friday Colin Campbell SaturdayNo Sunday *= Cheers, and kudos to David for his fixing and inventing! Colin ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Code from manual causes compilation warning
On Thu, Oct 3, 2013 at 5:49 PM, Urs Liska lilyli...@googlemail.com wrote: When following the Application Usage manual to use the '-e' command line option http://www.lilypond.org/doc/**v2.17/Documentation/usage/** command_002dline-usage.html#**basic-command-line-options-**for-lilypondhttp://www.lilypond.org/doc/v2.17/Documentation/usage/command_002dline-usage.html#basic-command-line-options-for-lilypond and writing #(use-modules (guile-user)) at the beginning of the document I get the following WARNING: #f: imported module (guile-user) overrides core binding `%module-public-interface' It is identical with different versions between 2.16.2 and 2.17.27. Is this warning something to care about or can I ignore it? In any case I think following the documentation shouldn't result in such a warning. Does this point to an issue with the recommended practice? Is it a false alarm that can/should be suppressed/avoided? Should it at least be mentioned in the documentation? Hi, Urs - Thanks for the email. It has been submitted as Issue 3613 : https://code.google.com/p/lilypond/issues/detail?id=3613 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bagpipe docs
On Mon, Oct 7, 2013 at 3:35 AM, Noeck noeck.marb...@gmx.de wrote:
in this section of the manual (2.16 as well as 2.17):
http://lilypond.org/doc/v2.16/Documentation/notation/bagpipes
the first mentioned advantage of bagpipe.ly is that \taor is short for
\grace { \small G32[ d G e] }
But this line is no valid syntax without bagpipe.ly (due to the G).
The meaning of pitches with bagpipe.ly should be explained before, not
afterwards. (A more minimal correction would be to change this line to
usual
lilypond syntax using , and ' .)
In addition, the commands of ly/bagpipe.ly should be explained, at least
on
of each type. Right now, the user needs to read bagpipe.ly to know the
commands.
Thanks, Noeck. This has been submitted as Issue 3614 :
https://code.google.com/p/lilypond/issues/detail?id=3614
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement: always print key signature grobs, even for keys with no sharps or flats
On Sat, Oct 12, 2013 at 11:58 AM, Paul Morris p...@paulwmorris.com wrote: Greetings bug squad, Say you want to override all key signature grobs, either to use a non-standard key signature system, or to enhance the traditional key signature system, as in this snippet: http://lsr.dsi.unimi.it/LSR/Item?id=856 ...unfortunately, for keys with no sharps or flats like C major and A minor, LilyPond does not always give you a key signature grob to override. For these keys LilyPond *does* put an empty (invisible) key signature grob at the beginning of the first line of music, and also any time the key changes to a key with no sharps or flats. However, LilyPond does *not* include an empty key signature grob at the beginning of any lines of music after the first. Greetings, Paul Morris - Thanks for the email. This has been submitted as Issue 3615 : https://code.google.com/p/lilypond/issues/detail?id=3615 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Path expansion in lilypond-book (and others)
On Wed, Jul 31, 2013 at 7:01 AM, Ralph Palmer ralphbugl...@gmail.comwrote: On Fri, Jul 26, 2013 at 5:55 PM, Chris Ritson chris.rit...@dunelm.org.ukwrote: From: Martin Tarenskeen Date: Fri, 22 Feb 2013 12:40:58 +0100 (CET) snip ERROR: In procedure primitive-load-path: ERROR: Unable to find file lily.scm in load path The clue to this is in a later posting from Robert Eckl. lilypond-book is using a construct os.path.abspath(os.path.dirname(sys.argv[0])) Greetings, Chris Ritson and BugList - I apologize for the late reply. This has been added as issue 3496 - https://code.google.com/p/lilypond/issues/detail?id=3496 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Path expansion in lilypond-book (and others)
On Fri, Jul 26, 2013 at 5:55 PM, Chris Ritson chris.rit...@dunelm.org.ukwrote: From: Martin Tarenskeen Date: Fri, 22 Feb 2013 12:40:58 +0100 (CET) snip ERROR: In procedure primitive-load-path: ERROR: Unable to find file lily.scm in load path The clue to this is in a later posting from Robert Eckl. lilypond-book is using a construct os.path.abspath(os.path.dirname(sys.argv[0])) to locate itself and then to find the lilypond share directory from there. On my system (now fedora 19) /bin is a symbolic link to /usr/bin, but there is no equivalent link for /share. /bin is (rightly from the old days of Unix Edition 6) before /usr/bin in my PATH. This leads to an invalid name for lily.scm. I think the right thing to do will be to add os.path.realpath to expand any symbolic links giving the following patch:- *** lilypond-book.orig 2013-07-26 22:29:10.369168798 +0100 --- lilypond-book 2013-07-26 22:28:30.423492984 +0100 *** *** 71,77 sys.path.insert (0, os.path.join (d, 'python')) # dynamic relocation, for GUB binaries. ! bindir = os.path.abspath (os.path.dirname (sys.argv[0])) for p in ['share', 'lib']: datadir = os.path.abspath (bindir + '/../%s/lilypond/current/python/' % p) sys.path.insert (0, datadir) --- 71,77 sys.path.insert (0, os.path.join (d, 'python')) # dynamic relocation, for GUB binaries. ! bindir = os.path.abspath (os.path.dirname (os.path.realpath (sys.argv[0]))) for p in ['share', 'lib']: datadir = os.path.abspath (bindir + '/../%s/lilypond/current/python/' % p) sys.path.insert (0, datadir) There appear to be similar issues in other places as well:- /usr/bin/abc2ly:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) /usr/bin/convert-ly:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) /usr/bin/etf2ly:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) /usr/bin/lilymidi:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) /usr/bin/lilypond-book:bindir = os.path.abspath (os.path.dirname (os.path.realpath (sys.argv[0]))) /usr/bin/lilysong:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) /usr/bin/midi2ly:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) /usr/bin/musicxml2ly:bindir = os.path.abspath (os.path.dirname (sys.argv[0])) Can this be turned into a bug suggestion, please? Chris Ritson Greetings, Chris Ritson - I will add this as an issue, but it would help to know what version of LilyPond you are using. Also, I'm running only Windows 7, and I'm not seeing this. Can anyone confirm whether or not this is occurring under Mac? Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: inconsistent treatment of vertical spacing variables?
eluzew@
gt; writes:
why do we have to specify a list for the
VerticalAxisGroup.staff-staff-spacing while e.g. for the
StaffGrouper.staff-staff-spacing you can define single items and also
all
the other vertical spacers like default-staff-staff-spacing,
nonstaff-relatedstaff-spacing, nonstaff-unrelatedstaff-spacing etc.
accept
single values?
\score {
\new PianoStaff \with {
\override VerticalAxisGroup.staff-staff-spacing.basic-distance = #35
}
\new Staff { c''1 c'' c''2 c'' }
\new Staff { \clef bass e1 f e2 d }
}
and here is part of the log:
GNU LilyPond 2.17.23
…
warning: type check for `staff-staff-spacing' failed; value
`((basic-distance . 35) . #unpure-pure-container #lt;primitive-procedure
ly:axis-group-interface::calc
:
:
taff-staff-spacing #primitive-procedure
ly:axis-group-interface::calc-pure-staff-staff-spacing )' must be of type
`list'
Eluze
Thanks, Eluze. This has been added as issue 3482 :
https://code.google.com/p/lilypond/issues/detail?id=3482
Developers or other Bug Listers : would this have been more appropriately
labeled as :
*Type-Sc*ripts = Problem or desired feature in the non-build-system scripts
?
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Invitation to connect on LinkedIn
LinkedIn I'd like to add you to my professional network on LinkedIn. - Ralph Ralph Palmer Retired at Home Springfield, Massachusetts Area Confirm that you know Ralph Palmer: https://www.linkedin.com/e/-ei0hyc-hjr07h7z-6h/isd/15380797173/Zf2qWks4/?hs=falsetok=36ds9kuL0tKBQ1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-ei0hyc-hjr07h7z-6h/v9WAHNRFrvuTdl9uIXopzIrnONGp94RV/goo/bug-lilypond%40gnu%2Eorg/20061/I5120570912_1/?hs=falsetok=2oaLMNe8wtKBQ1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \displayLilyMusic with full measure rest and \markup not working
On Wed, Jul 10, 2013 at 3:12 AM, Eluze elu...@gmail.com wrote:
reported by Gilles THIBAULT on the LilyPond French Users' list:
http://lilypond-french-users.1298960.n2.nabble.com/bug-displayLilyMusic-td7580136.html
the code
music = { R1-\fermataMarkup }
\displayLilyMusic \music
produces
C:/Program Files
(x86)/LilyPond/usr/share/lilypond/current/scm/define-music-display-methods.scm:68:16:
In procedure car in expression (car markup-expr):
C:/Program Files
(x86)/LilyPond/usr/share/lilypond/current/scm/define-music-display-methods.scm:68:16:
Wrong type (expecting pair): ()
this seems to have been introduced somewhere after version 2.12.3 (correct)
( 2.13.12 is corrupted)
Eluze
Is this related to Issue 2067? I don't have enough experience to determine
whether it is or not. I'm submitting it as a new issue - Issue 3463 - with
a comment.
https://code.google.com/p/lilypond/issues/detail?id=3463colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary
Thanks for the report, Eluze,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Footnotes inside header markups
On Wed, Jul 10, 2013 at 10:08 PM, Barikavily barikav...@gmail.com wrote:
I'm not top posting.
\version 2.16.2
% Footnotes don't work when located inside a header block
% (Same thing happens with auto-footnote)
\markup {
Top-level markup
\footnote * \italic * This is my top-level markup footnote
}
\score {
{ c' }
\header {
piece = \markup {
Piece markup
\footnote ** \italic ** Footnote about the
piece title
}
}
}
As far as I can tell, no one else has replied to Barikavily, so here goes .
. .
From the documentation, it looks to me like \footnote is intended to be
used only with music, not with headers. Is that a correct interpretation,
LilyPonders? If so, the behavior you describe, Barikavily, is the intended
behavior.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: vertical spacing in leadsheet with text between staffs
On Mon, Jul 15, 2013 at 4:33 PM, Jürgen Spiekermann
juergen.spiekerm...@t-online.de wrote:
I'm not top posting.
Hello,
the following example shows two staffs with a Text between the staff:
\version 2.16.2
\paper {
#(set-paper-size a5)
print-page-number = ##f
ragged-right = ##f
ragged-last-bottom = ##t
ragged-bottom = ##t
}
\layout {
indent = 0.0\cm
}
\new ChordNames{ \germanChords \chordmode{ \germanChords f1 c1 c1
f1} }
\relative c' {
\time 4/4
\key f \major
f4 f f f g e c2 g'4 g f g a2 f2
}
\addlyrics { \set stanza = #1. Chris -- tus lädt uns al -- le
ein, wir
sind sei -- ne Gäs -- te. }
\markup{\bold Zwischenvers}
\new ChordNames{ \germanChords \chordmode{ \germanChords g1:7 c1
g1:7 c1 } }
\relative c' {
\time 4/4
\key f \major
g'4 g a b c2 a g4 a g f e2 d \bar |.
}
\addlyrics { \set stanza = #1.-2. Seg -- ne, was wir ge -- ben,
seg -- ne
un -- ser Le -- ben! }
The second staff is printed with huge space between Text and staff.
Ist this a bug? It does not happen without \addlyrics
Greetings, Jürgen Spiekermann -
This appears to be a bug, or at least ugly behavior. Thank you for your
report. A tracker has been issued as Issue 3464 :
https://code.google.com/p/lilypond/issues/detail?id=3464
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Pitched trill layout
On Tue, Jul 16, 2013 at 7:48 AM, Timothy Lanfear
lanf...@costamagna.demon.co.uk wrote:
I'm not top posting
Layout of pitched trills with an interval greater than a third became worse
in 2.17.10.
\version 2.17.10
\relative c' {
\pitchedTrill f2 \startTrillSpan g r2 \stopTrillSpan
\pitchedTrill f2 \startTrillSpan a r2 \stopTrillSpan
\pitchedTrill f2 \startTrillSpan b r2 \stopTrillSpan
}
Thanks for the report, Timothy Lanfear. This has been submitted as Issue
3465.
https://code.google.com/p/lilypond/issues/detail?id=3465
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: with point-stencil NoteHead and slur certain textscripts can't be written
On Mon, Jul 1, 2013 at 4:49 AM, Eluze elu...@gmail.com wrote:
with version 2.17.21 the code:
{
\override NoteHead #'stencil = #point-stencil
c'2.-po ( b8 a )-- g1-
}
produces:
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
writing abc or other text is fine
using apostrophes or \markup doesn't help
older versions work fine
in issue 3106 a similar message is displayed
Eluze
Thanks for the report, Eluze. It has been added as issue 3434 :
https://code.google.com/p/lilypond/issues/detail?id=3434
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Vacation
On Sat, Jun 8, 2013 at 5:13 PM, Eluze elu...@gmail.com wrote: hi Ralph no problem - I'll try to take over on late afternoon on Tuesdays Thanks, Eluze. I'm back, and can take over Tuesdays again. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Vacation
Greetings, fellow Bug Listers - I apologize for having been sloppy about my participation for the last month or so, and I must confess I'm about to be worse for about three weeks. I'll be on a road trip until the beginning of July, and my internet availability may be spotty. I would appreciate it if others could cover for me (Tuesdays) for the rest of June. Thanks in advance, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Articulate of short \prall
On Fri, May 24, 2013 at 6:45 PM, Hans Aberg haber...@telia.com wrote:
The articulate.ly file (tried with LilyPond 2.16.0) cannot handle
\prall applied to a 16th note, as in the example below, which is used in
Balkan music. In the example below, the first 4th note indicates this use,
and the second the expansion I would prefer: just ignore moving back to the
ornament main note. Currently, it squeezes an 8th note in, with the error
programming error: Going back in MIDI time.
\include articulate.ly
music =
\new Staff {
\tempo 4 = 120
\time 2/4
\relative c' {
d16 c\prall b a d16 c32 d b16 a |
}
}
\score {
\music
\layout {}
}
\score {
\unfoldRepeats \articulate \music
\midi {}
}
I do not like to do this, but I'm going to have to ask someone else on the
bug list to evaluate this. I cannot distinguish what's going on in the midi
file to tell whether midi is behaving the way Hans Aberg says, nor do I
know exactly how articulate.ly is supposed to behave. It does appear to me
that \prall, if it's behaving the way Hans Aberg says it is, is behaving
the way I would expect an upper pralltriller, or upper mordent, to behave.
Is Hans Aberg requesting a new feature?
Would someone else on the bug list please take over this report?
Thank you,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement request: stretched text in text spanners
On Wed, May 15, 2013 at 7:51 AM, Peter Toye lilyp...@ptoye.com wrote: I want to put text like rallen---tan---do into some music. I've noticed that the mailing list also had someone who wanted to put cres---cendo similarly. The current text spanner cannot do this, and various people have suggested workarounds. The main problem is that with a simple text spanner, each item of text is separate from the next, and the heights can vary. I'm a newbie to Lilypond, so I'm afraid that I can't really help by suggesting a syntax for a replacement that would be compatible with LP's design methods, but I'm sure that someone here can do this! Greetings, Peter Toye - This has been added as Issue 3373 : https://code.google.com/p/lilypond/issues/detail?id=3373 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: crash with \partcombine \repeat tremolo when voices cross
On Fri, May 17, 2013 at 4:41 AM, Eluze elu...@gmail.com wrote: reported in the French community http://lilypond-french-users.1298960.n2.nabble.com/Probleme-avec-repeat-tremolo-en-partcombine-tp7579661.html I couldn't find this in the many issues about \partcombine you can circumvent this problem by adding explicit beaming in both voices for the critical notes (but dozens of warnings and errors still appear) Thanks, Eluze. This has been added as Issue 3374 : https://code.google.com/p/lilypond/issues/detail?id=3374 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hampered installation on Windows 7 pro
On Wed, May 1, 2013 at 2:28 AM, Jan Nieuwenhuizen jann...@gnu.org wrote: Hi, I experienced an unfriendly installation on Windows 7 pro, similar to what was mentioned in http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00226.html * You need to run lilypond-setup.exe as admininstator (even if you already have administrator rights * LilyPad with Welcome_to_LilyPond.ly does not pop up when you click on the lilypond icon, until after you explicitly run lilypond as admininstrator once After that, it works fine. It would be nice if these setup hurdles were fixed, or at least they should be documented for now. Greetings, Jan Thanks for the email, Jan Nieuwenhuizen. This has been entered as Issue 3343 : https://code.google.com/p/lilypond/issues/detail?id=3343 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Empty staves not removed after one-bar percent repeat
On Tue, Apr 16, 2013 at 12:39 PM, Peter Crighton
petecrigh...@googlemail.com wrote:
% Empty staves are not removed after a percent repeat of one bar. Two or
more
bars work fine.
\version 2.16.2
\paper { ragged-right = ##t }
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
\relative c' {
\repeat unfold 4 { c1 }
\break
R1*4
\break
\repeat percent 4 { c1 }
\break
R1*4
\break
\repeat percent 2 { c1 c }
\break
R1*4
}
Thanks, Peter Crighton. This has been submitted as issue 3321 :
https://code.google.com/p/lilypond/issues/detail?id=3321
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fingering with guide indications difference 2.16.2 - 2.17.11
On Mon, Feb 4, 2013 at 9:25 PM, Nick Payne nick.pa...@internode.on.netwrote: The code below (I think it might have come from David Nalesnik) builds without any error on both 2.16.2 and 2.17.11, but the output is correct on 2.16.2 and incorrect on 2.17.11. On 2.17.11, the fingerings with guide indication that are to the left become centred on the note - on 2.16 they stay in the correct position to the left. Is this difference anything to do with the fingering changes that were introduced earlier in 2.17? Nick Thanks, Nick. This has been submitted as issue 3171 : http://code.google.com/p/lilypond/issues/detail?id=3171 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bass figures are not horizontally aligned to whole notes
On Wed, Feb 6, 2013 at 4:13 PM, Marek Klein ma...@gregoriana.sk wrote:
Hello,
2013/2/2 Xavier Scheuer x.sche...@gmail.com
My guess is that bass figures should indeed be centered on the note
heads (note column), so default behaviour should be changed accordingly.
But only the figures. Accidentals, +, etc. should not be taken into
account in the centering, contrary to Bertrand's first workaround.
If someone possessing a reference book could confirm this, thanks.
Could this be considered as the minimal example and the bad output?:
\new Staff { \clef F c1 c c \bar |.}
\new FiguredBass \figuremode {
51 6 4+ 2\+ 6
}
Marek
Thanks, Marek and Xavier, and my apologies, Marek, for misreading your name
and calling you Mark. This has been submitted as issue 3172 :
http://code.google.com/p/lilypond/issues/detail?id=3172
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Extra leading repeat sign with leading rest and lyrics
On Mon, Jan 28, 2013 at 10:44 PM, Todd Hesla todd.he...@gmail.com wrote: I'm not top posting. % When processing a volta repeat containing a leading rest and lyrics, % Lilypond 2.14.2 adds an extra leading repeat sign where the lyrics start % (after the rest). Thanks for the report, Todd Hesla. This has been entered as Issue 3149 : http://code.google.com/p/lilypond/issues/detail?id=3149 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Squad Rota
I think this schedule meets those constraints: Mon - Eluze Tue - Ralph Wed - Marek Thu - Joe Wakeling (soon) Fri - Colin H Sat - Colin H Sun - Federico Everyone happy with that? Works for me. Thanks, everyone! Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug Squad Rota
On Mon, Jan 7, 2013 at 8:36 AM, Marek Klein ma...@gregoriana.sk wrote: Hello Colin, 2013/1/7 Colin Hall colingh...@gmail.com Marek, would you like me to take one of your days? If you can do other staff for lilipond instead - then do it. If you prefer doing bug squad duties, I prefer to get rid of friday... Marek Whoa! I'm getting confused. Where does it stand now? I repeat my earlier request to take a weekday. If Federico is joining us, could we figure out a rota that would move me off of Saturday? I'd be happy to take either of Marek's days or either of Colin's days, but not if it means switching to Sunday. Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: some way of manually breaking slurs, ties and lyric extenders
On Sun, Dec 16, 2012 at 1:11 PM, Ben Rudiak-Gould benrud...@gmail.comwrote:
I have hacked something up (see code below), but it doesn't work very well:
* It works for slurs on either end as long as they span at least two
notes. I can get it to work with single-note slurs at the end of the
line by writing c'( s1*0) or c'( ), but I get the warning
programming error: bounds of this piece aren't breakable. I haven't
found a way to make it work with single-note slurs at the beginning of
the line.
* It works for lyric hyphens and extenders if there's an extra note
with no lyric to extend to. I have to use as the lyric for this
note, not _. This has the side effect that the lyric syllable isn't
aligned properly at the end of the line (it's centered under the note
instead of left-aligned).
* I can't get it to work for ties in either direction no matter what I try.
* It doesn't do anything to explicit beams (not that I suppose anyone
would want to break beams this way), and it doesn't work properly with
ligature brackets or tuplet brackets -- the bracket extends to the bar
line but appears to begin/end there instead of being broken.
MS, I hope you can tell me if there's a way to work around these
problems in Scheme alone.
-- Ben
8
\version 2.17.9
% This is necessary to avoid a warning
#(set-object-property! 'fake-break-left 'backend-type? boolean?)
#(set-object-property! 'fake-break-right 'backend-type? boolean?)
#(define (fake-break-engraver score-context)
(let ((last-barline #f) (open-spanners '()))
(define (handle-barline barline)
(set! last-barline barline)
(set! open-spanners (filter try-extend-right open-spanners)) )
(define (try-extend-right spanner)
(let ((still-open (null? (ly:spanner-bound spanner RIGHT
(if (not still-open)
(ly:spanner-set-bound! spanner RIGHT last-barline) )
still-open ))
(define (handle-spanner-start spanner)
(if (eq? #t (ly:grob-property spanner 'fake-break-left))
(if last-barline
(ly:spanner-set-bound! spanner LEFT last-barline) ))
(if (eq? #t (ly:grob-property spanner 'fake-break-right))
(set! open-spanners (cons spanner open-spanners)) ))
`((acknowledgers
(paper-column-interface .
,(lambda (engraver grob source-engraver)
(if (and (eq? 'NonMusicalPaperColumn
(assoc-ref (ly:grob-property grob 'meta) 'name) )
(not (null? (ly:grob-property grob 'measure-length)))
)
(handle-barline grob) )))
(spanner-interface .
,(lambda (engraver grob source-engraver)
(handle-spanner-start grob) ))
\layout { \context { \Score \consists #fake-break-engraver } }
\paper { ragged-right = ##t }
\score {
\new Staff {
c' d' \once \override PhrasingSlur #'fake-break-right = ##t e'\( f'\)
}
\addlyrics {
First to \once \override LyricHyphen #'fake-break-right = ##t sec --
}
\new Staff {
\once \override Slur #'fake-break-left = ##t g'( a') b'2
}
\addlyrics {
\once \override LyricHyphen #'fake-break-left = ##t _ -- ond.
}
\new Staff {
c'16 c' c' c' c'4 c' c'16 c' c' c'
}
}
8
Greetings, Ben Rudiak-Gould -
I was hoping someone else would respond, but I haven't seen anything, so
here goes . . .
I know almost nothing about Scheme, so I won't try to evaluate your
snippet. However, the function would be valuable, so I would encourage you
to submit your snippet to the Snippet Repository so that others can use it.
Do you want to make this a feature request?
All the best,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Bug Squad Rota
Greetings Colin, Bug Squaders, and Developers - Thanks, Colin, for running the scripts and reporting the Bug squad metrics. I have a request to make. I live in the eastern U.S., and at least some of the Bug Squaders appear to live in Europe. My usual (most reliable) time on the computer on the weekend is in the morning. As a result, I frequently don't have any bugs to evaluate when I get up on Saturday morning, and I frequently don't get back to the Bug List until Sunday morning. By that time, someone in Europe has usually snagged my Saturday bugs. In the interest of equity of labor, I'm requesting that someone who has one of the weekdays (where I'm more often at the computer later in the day) switch with me. If no one wishes to switch, I can stay on Saturday, but I probably won't catch as many bugs as I ought. I appreciate your time, your attention, and your help, Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
On Sun, Dec 30, 2012 at 6:35 AM, Federico Bruni fedel...@gmail.com wrote: Hi I have two different questions (quite related to each other) 1) In NR 1.2.2, Full measure rests The snippet multi-measure-rest-markup.ly says: Markups attached to a multi-measure rest will be centered above or below it. Long markups attached to multi-measure rests do not cause the measure to expand. To expand a multi-measure rest to fit the markup, use a spacer rest with an attached markup before the multi-measure rest. Note that the spacer rest causes a bar line to be inserted. I cannot understand the last sentence. I cannot see any change in the bar lines if I comment the spacer rests. Greetings, Federico and other LilyPonders - Please forgive me, but I cannot see how I can comment out the spacer rests without either commenting out the \markup s or replacing the spacer rests with . Am I missing something? Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
On Sun, Dec 30, 2012 at 6:35 AM, Federico Bruni fedel...@gmail.com wrote:
2) Should s1*0 be replaced by (see issue 2522)?
Two snippets still use s1*0
$ cd Documentation/snippets
$ git grep 's1\*0'
multi-measure-rest-markup.ly: s1*0^\markup { [MAJOR GENERAL] }
multi-measure-rest-markup.ly: s1*0_\markup { \italic { Cue: ... it is
yours } }
multi-measure-rest-markup.ly: s1*0^\markup { A }
positioning-segno-and-coda-**with-line-break.lyhttp://positioning-segno-and-coda-with-line-break.ly:
% | s1*0^\markup { D.S. al
positioning-segno-and-coda-**with-line-break.lyhttp://positioning-segno-and-coda-with-line-break.ly:
% | s1*0^\markup { \center
Greetings, Federico and other LilyPonders -
I agree that it looks like these are candidates for , but I don't believe
they belong on the Bug List. Would you like to write new snippets,
Federico? The same goes for anyone else out there who's ambitious.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
