Re: \acciaccatura before barline?
Father Gordon Gilbert writes: > Thanks guys. That did the trick. > > Rather than set to ##t and ##f all the time, I did > > dsl = \set doubleSlurs = ##t > dso = \set doubleSlurs = ##f > > and then used \dsl and \dso as needed. > > Lily is truly amazing! \once\dsl should also work with a reasonably current 2.15. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
multimeasure rests
Dear community,
because I'm awfully bad in mathematics I wrote a function for calculating
the correct length of multimeasure rests.
Although it doesn't cause a crash (which is a huge sucess for me as a
"programmer"), it doesn't work as expected. Instead of showing one goupt of
multimeasure rests, it shows every single multimeasure rest.
Does someone have an idea to avoid the problem?
Here is my snippet:
%
\version "2.14.2"
xR = #(define-music-function (parser location ANFANG LAST x ) (number?
number? ly:music? )
#{ %
\repeat unfold $(+ 1(- LAST ANFANG)) $x
#})
\layout { \context { \Score skipBars = ##t } }
\new Staff {
R1*5 % this works as expected
\xR #6 #11 R1 % this, unfortunately, not, it shows 6 single barrests
c'1
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: multimeasure rests
Stefan Thomas writes:
> Dear community,
> because I'm awfully bad in mathematics I wrote a function for
> calculating the correct length of multimeasure rests.
> Although it doesn't cause a crash (which is a huge sucess for me as a
> "programmer"), it doesn't work as expected. Instead of showing one
> goupt of multimeasure rests, it shows every single multimeasure rest.
> Does someone have an idea to avoid the problem?
*x is not a shorthand for \repeat unfold but a duration modifier.
> Here is my snippet:
> %
> \version "2.14.2"
> xR = #(define-music-function (parser location ANFANG LAST x )
> (number? number? ly:music? )
> #{ %
> \repeat unfold $(+ 1(- LAST ANFANG)) $x
> #})
> \layout { \context { \Score skipBars = ##t } }
> \new Staff {
> R1*5 % this works as expected
> \xR #6 #11 R1 % this, unfortunately, not, it shows 6 single
> barrests
> c'1
> }
If you can't keep your newsreader from completely mangling examples (it
contains unbreakable spaces as well as line breaks in comments), you
should likely try attaching the examples as a file instead.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: multimeasure rests
David Kastrup writes:
> Stefan Thomas writes:
>
>> Dear community,
>> because I'm awfully bad in mathematics I wrote a function for
>> calculating the correct length of multimeasure rests.
>> Although it doesn't cause a crash (which is a huge sucess for me as a
>> "programmer"), it doesn't work as expected. Instead of showing one
>> goupt of multimeasure rests, it shows every single multimeasure rest.
>> Does someone have an idea to avoid the problem?
>
> *x is not a shorthand for \repeat unfold but a duration modifier.
>
>> Here is my snippet:
>> %
>> \version "2.14.2"
>> xR = #(define-music-function (parser location ANFANG LAST x )
>> (number? number? ly:music? )
>> #{ %
>> \repeat unfold $(+ 1(- LAST ANFANG)) $x
>> #})
>> \layout { \context { \Score skipBars = ##t } }
>> \new Staff {
>> R1*5 % this works as expected
>> \xR #6 #11 R1 % this, unfortunately, not, it shows 6 single
>> barrests
>> c'1
>> }
>
> If you can't keep your newsreader from completely mangling examples (it
> contains unbreakable spaces as well as line breaks in comments), you
> should likely try attaching the examples as a file instead.
Actually, this was because you sent the mail as a mixed HTML/plain text
mail. You'll make the average reader of mailing list articles (and of
mail in general) quite happier if you stop your mail client from
wastefully creating duplicate HTML content that is not even properly
usable (in this case). Switching to the plain text copy, I got the
example out fine.
Try the following:
%
\version "2.14.2"
xR = #(define-music-function (parser location ANFANG LAST x ) (number?
number? ly:music? )
#{ \scaleDurations #$(cons (+ 1(- LAST ANFANG)) 1) $x #})
\layout { \context { \Score skipBars = ##t } }
\new Staff {
R1*5 % this works as expected
\xR #6 #11 R1 % this, unfortunately, not, it shows 6 single barrests
c'1
}
I can't vouch for it being correct, not having 2.14 along anymore (the
syntax for 2.15.22 is slightly different and one could do this much
easier anyway).
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 110, Issue 8
Dear David,
thanks for Your answer, Your code works fine in 2.14.2.
Sorry for the problems with html, I'm just using the
goggle-mail-client. maybee it will work better, when I write without
formatting.
2012/1/4
>
> Send lilypond-user mailing list submissions to
> lilypond-user@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
> lilypond-user-requ...@gnu.org
>
> You can reach the person managing the list at
> lilypond-user-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
>
>
> Today's Topics:
>
> 1. Re:\acciaccatura before barline? (David Kastrup)
> 2. multimeasure rests (Stefan Thomas)
> 3. Re:multimeasure rests (David Kastrup)
> 4. Re:multimeasure rests (David Kastrup)
>
>
> --
>
> Message: 1
> Date: Wed, 04 Jan 2012 09:43:11 +0100
> From: David Kastrup
> To: lilypond-user@gnu.org
> Subject: Re: \acciaccatura before barline?
> Message-ID: <87sjjvkgdc@fencepost.gnu.org>
> Content-Type: text/plain
>
> Father Gordon Gilbert writes:
>
> > Thanks guys. That did the trick.
> >
> > Rather than set to ##t and ##f all the time, I did
> >
> > dsl = \set doubleSlurs = ##t
> > dso = \set doubleSlurs = ##f
> >
> > and then used \dsl and \dso as needed.
> >
> > Lily is truly amazing!
>
> \once\dsl should also work with a reasonably current 2.15.
>
> --
> David Kastrup
>
>
>
>
> --
>
> Message: 2
> Date: Wed, 4 Jan 2012 10:05:47 +0100
> From: Stefan Thomas
> To: lilypond-user
> Subject: multimeasure rests
> Message-ID:
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dear community,
> because I'm awfully bad in mathematics I wrote a function for calculating
> the correct length of multimeasure rests.
> Although it doesn't cause a crash (which is a huge sucess for me as a
> "programmer"), it doesn't work as expected. Instead of showing one goupt of
> multimeasure rests, it shows every single multimeasure rest.
> Does someone have an idea to avoid the problem?
> Here is my snippet:
> %
> \version "2.14.2"
> xR = #(define-music-function (parser location ANFANG LAST x ) (number?
> number? ly:music? )
> #{ %
> \repeat unfold $(+ 1(- LAST ANFANG)) $x
> #})
> \layout { \context { \Score skipBars = ##t } }
> \new Staff {
> R1*5 % this works as expected
> \xR #6 #11 R1 % this, unfortunately, not, it shows 6 single barrests
> c'1
> }
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> <http://lists.gnu.org/archive/html/lilypond-user/attachments/20120104/b757a236/attachment.html>
>
> --
>
> Message: 3
> Date: Wed, 04 Jan 2012 10:12:09 +0100
> From: David Kastrup
> To: lilypond-user@gnu.org
> Subject: Re: multimeasure rests
> Message-ID: <87k457kf12@fencepost.gnu.org>
> Content-Type: text/plain; charset=iso-8859-1
>
> Stefan Thomas writes:
>
> > Dear community,
> > because I'm awfully bad in mathematics I wrote a function for
> > calculating the correct length of multimeasure rests.
> > Although it doesn't cause a crash (which is a huge sucess for me as a
> > "programmer"), it doesn't work as expected. Instead of showing one
> > goupt of multimeasure rests, it shows every single multimeasure rest.
> > Does someone have an idea to avoid the problem?
>
> *x is not a shorthand for \repeat unfold but a duration modifier.
>
> > Here is my snippet:
> > %
> > \version "2.14.2"
> > xR = #(define-music-function (parser location? ANFANG? LAST x )
> > (number? number? ly:music??? )
> > ??? #{ %
> > ??? \repeat unfold $(+ 1(- LAST ANFANG))? $x
> > #})
> > \layout { \context { \Score skipBars = ##t } }
> > \new Staff {
> > ?? R1*5 % this works as expected
> > ?? \xR #6 #11 R1 % this, unfortunately, not, it shows? 6 single
> > barrests
> > ? c'1
> > }
>
> If you can't keep your newsreader from completely mangling examples (it
> contains unbreakable spaces as well as line breaks in comments), you
> should likely try attaching the examples as a file instead.
>
> --
> David Kastrup
>
>
>
>
> --
Re: lilypond-user Digest, Vol 110, Issue 8
Stefan Thomas writes: > Dear David, > thanks for Your answer, Your code works fine in 2.14.2. > Sorry for the problems with html, I'm just using the > goggle-mail-client. maybee it will work better, when I write without > formatting. You replied to a message digest instead of a message. And you quoted the whole digest. Your full quote of the previous digest will appear in the next digest. If people do this kind of abuse more often than once per digest, the size of the digests will grow exponentially, with the useful content decreasing in the same proportion. _Please_ make it a habit to _never_ _ever_ quote _anything_ except what you are _explicitly_ referring to. Everything else can be retrieved, if required, by using the normal mail and news tools. And _never_ _ever_ reply to a digest. That screws up the threading and context of messages. Thank you. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Some drum notation questions
I have been using lilypond for years for my own projects and have recently introduced it to a friend of mine. He is a drum instructor and has been reading drum notation for many years. He's pointed out some things that are non-standard about the way lilypond handles some drum notation tasks. Most of these I have been able to correct using a #(define block. There are, however, some things I have not yet been able to crack. First, for hi-hat, the notation for open and closed are correct, but for the half-open he would like to appear exactly like the open hi-hat notation, except the "o" above the stem of the note needs to have a single slash through it. Also, the note head for a China cymbal he notes by having a standard cross note head, but with a box around it. Can anyone point me in the right direction for making these changes? Thanks, Vaylor Trucks ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Lyrics and polyphony
\version "2.12.2"
{
4<< { b'1 } \\ { g'4( f' e'2) } >>
}
\addlyrics {
Ex -- cel -- lent Thy name! % The last word does not appear
}
Hello all!
I have a question concerning lyrics and polyphony. I have looked through the
Snippet Repository, but came up with nothing.
The music I am typesetting is four-part harmony, and for the most part each part
has the same note durations, and entering them as chords makes sense. However,
in a few places they differ, and while I have figured out how to make the notes
look correctly within angle brackets << >> (see above) the lyrics will not stick
to this part of the music (I guess because I made a new context). Is there a way
to have the lyrics work with this setup? Or perhaps is there an altogether
different way I should go about this?
Thanks!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and polyphony
Hello,
On 4 January 2012 18:28, Benjamin Bruce wrote:
> \version "2.12.2"
> {
> 4<< { b'1 } \\ { g'4( f' e'2) } >>
> }
> \addlyrics {
> Ex -- cel -- lent Thy name! % The last word does not appear
> }
>
> Hello all!
> I have a question concerning lyrics and polyphony. I have looked through the
> Snippet Repository, but came up with nothing.
>
> The music I am typesetting is four-part harmony, and for the most part each
> part
> has the same note durations, and entering them as chords makes sense. However,
> in a few places they differ, and while I have figured out how to make the
> notes
> look correctly within angle brackets << >> (see above) the lyrics will not
> stick
> to this part of the music (I guess because I made a new context). Is there a
> way
> to have the lyrics work with this setup? Or perhaps is there an altogether
> different way I should go about this?
>
I don't know much about lyrics but I think this might be the place in the doc
http://lilypond.org/doc/v2.14/Documentation/notation/techniques-specific-to-lyrics#divisi-lyrics
regards
--
--
James
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Some drum notation questions
Hello, On 4 January 2012 18:32, Vaylor Trucks wrote: > I have been using lilypond for years for my own projects and have recently > introduced it to a friend of mine. He is a drum instructor and has been > reading > drum notation for many years. He's pointed out some things that are > non-standard about the way lilypond handles some drum notation tasks. Most of > these I have been able to correct using a #(define block. There are, however, > some things I have not yet been able to crack. > > First, for hi-hat, the notation for open and closed are correct, but for the > half-open he would like to appear exactly like the open hi-hat notation, > except > the "o" above the stem of the note needs to have a single slash through it. > > Also, the note head for a China cymbal he notes by having a standard cross > note > head, but with a box around it. > > Can anyone point me in the right direction for making these changes? I have no experience of doing this but you might want to start here http://lilypond.org/doc/v2.14/Documentation/notation/modifying-stencils The percussion notes are all here: http://lilypond.org/doc/v2.14/Documentation/notation/percussion-notes -- -- James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Chord fingering placement bug?
See below. If the note with the accidental appears first in the chord,
then the fingering for the other note correctly avoids the accidental.
If the order of the notes is reversed, the fingering collides with the
accidental. I don't know if this is related to issue 1222
(http://code.google.com/p/lilypond/issues/detail?id=1222), also
concerning fingering colliding with an accidental.
\version "2.15.23"
\relative c'' {
\set fingeringOrientations = #'(left)
1
}
Nick
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and polyphony
On 5/01/2012, at 7:28 am, Benjamin Bruce wrote:
> \version "2.12.2"
> {
> 4<< { b'1 } \\ { g'4( f' e'2) } >>
> }
> \addlyrics {
> Ex -- cel -- lent Thy name! % The last word does not appear
> }
The problem is that the double backslash automagically creates _two_ new
voices; you only want one, with the other being a continuation of the original
voice. The solution is to create the new voice explicitly:
{
4<< {\voiceOne b'1 } \new Voice {
\voiceTwo g'4( f' e'2) } >>
}
\addlyrics {
Ex -- cel -- lent Thy name! % The last word does now appear
}
(The \voiceOne and \voiceTwo don't affect the lyrics, only the note stems.)
> The music I am typesetting is four-part harmony
In that case, personally, I'd write it as four parts rather than as chords.
Best wishes,
Matthew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Some drum notation questions
On 1/4/12 11:32 AM, "Vaylor Trucks" wrote: > >First, for hi-hat, the notation for open and closed are correct, but for >the >half-open he would like to appear exactly like the open hi-hat notation, >except >the "o" above the stem of the note needs to have a single slash through >it. > >Also, the note head for a China cymbal he notes by having a standard >cross note >head, but with a box around it. > >Can anyone point me in the right direction for making these changes? > >Thanks, >Vaylor Trucks The half-open hihat you describe is shown in the Notation Reference, section 2.5.1 under the heading "Custom Percussion Staves". As far as I know, there is currently no notehead that is a cross with a box around it. This would require you to define a custom notehead, which can be done by writing your own stencil procedure to replace ly:note-head::print. I'd be willing to create a glyph for the China cymbal note if you can give me a scan of a well-designed China cymbal note-head. HTH, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and polyphony
On 1/4/12 11:28 AM, "Benjamin Bruce" wrote:
>\version "2.12.2"
>{
> 4<< { b'1 } \\ { g'4( f' e'2) } >>
>}
>\addlyrics {
> Ex -- cel -- lent Thy name! % The last word does not appear
>}
>
>Hello all!
>I have a question concerning lyrics and polyphony. I have looked through
>the
>Snippet Repository, but came up with nothing.
>
>The music I am typesetting is four-part harmony, and for the most part
>each part
>has the same note durations, and entering them as chords makes sense.
>However,
>in a few places they differ, and while I have figured out how to make the
>notes
>look correctly within angle brackets << >> (see above) the lyrics will
>not stick
>to this part of the music (I guess because I made a new context). Is
>there a way
>to have the lyrics work with this setup? Or perhaps is there an altogether
>different way I should go about this?
Please see the Notation Reference, section 1.5.2. In particular, look at
Temporary polyphonic passages.
And may I invite you to consider upgrading to 2.14? It's better than 2.12
in a number of ways.
HTH,
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and polyphony
On 4 January 2012 23:32, Carl Sorensen wrote:
>
> Please see the Notation Reference, section 1.5.2. In particular, look at
> Temporary polyphonic passages.
This problem pops up often. I remember having replied to dozens of e-mails
—both on the French users mailing list and on lilypond-user— from
confused users about this. This is indeed explained in the notation
reference that
"[The << {...} \\ {...} >> construct] behaves differently to the
similar construct without the double backslashes: all the expressions
within this construct are assigned to new Voice contexts."
but could it be added that this implies the (dynamic) spanners, lyrics
associated to voice, etc. cannot be used from outside to inside the
<< {...} \\ {...} >> construct (and vice versa)?
And would it be possible to put a "warning box" or so around this?
Maybe we could add also a similar warning in the learning manual,
LM 3.2.1 I’m hearing Voices.
What do you think? James?
Of course the best would be to "solve" issue #1316 …
http://code.google.com/p/lilypond/issues/detail?id=1316
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chord fingering placement bug?
On 05/01/12 07:58, Nick Payne wrote:
See below. If the note with the accidental appears first in the chord,
then the fingering for the other note correctly avoids the accidental.
If the order of the notes is reversed, the fingering collides with the
accidental. I don't know if this is related to issue 1222
(http://code.google.com/p/lilypond/issues/detail?id=1222), also
concerning fingering colliding with an accidental.
\version "2.15.23"
\relative c'' {
\set fingeringOrientations = #'(left)
1
}
p.s. I also think that Lilypond's default spacing places fingering is
too far away from the note. It looks better, and is less confusing (see
also issue 220) with the following overrides:
\relative c'' {
\set fingeringOrientations = #'(left)
1
\override Fingering #'padding = #0.3
\override Staff.AccidentalPlacement #'left-padding = #0
}
Nick
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Some drum notation questions
Hi,
2012/1/4 Carl Sorensen :
> On 1/4/12 11:32 AM, "Vaylor Trucks" wrote:
>
>>
>>First, for hi-hat, the notation for open and closed are correct, but for
>>the
>>half-open he would like to appear exactly like the open hi-hat notation,
>>except
>>the "o" above the stem of the note needs to have a single slash through
>>it.
>>
>>Also, the note head for a China cymbal he notes by having a standard
>>cross note
>>head, but with a box around it.
>>
>>Can anyone point me in the right direction for making these changes?
>>
>>Thanks,
>>Vaylor Trucks
>
> The half-open hihat you describe is shown in the Notation Reference,
> section 2.5.1
> under the heading "Custom Percussion Staves".
>
> As far as I know, there is currently no notehead that is a cross with a
> box around it. This would require you to define a custom notehead, which
> can be done by writing your own stencil procedure to replace
> ly:note-head::print.
>
> I'd be willing to create a glyph for the China cymbal note if you can give
> me a scan of a well-designed China cymbal note-head.
>
> HTH,
>
> Carl
it would be nice to use a glyph with a box around a cross.
This might be a hackish work-around:
\version "2.14.2"
#(define glyph-types '("0laThin"
"1laThin"
"2laThin"))
customChineseCymbalNoteHead = \override NoteHead #'stencil =
#(lambda (grob)
(let* ((gl (ly:grob-property grob 'glyph-name))
(dur (ly:grob-property grob 'duration-log)))
(if (member gl glyph-types)
(ly:stencil-add
(grob-interpret-markup grob (markup #:fontsize 1.65
#:musicglyph "noteheads.s1laFunk"))
(if (or (= dur 1) (= dur 0))
(grob-interpret-markup grob (markup #:fontsize -2.25
#:musicglyph "noteheads.s1cross"))
(grob-interpret-markup grob (markup #:fontsize -1.25
#:musicglyph "noteheads.s2cross"
(ly:note-head::print grob
#(define my-drums '((halfopenhihat cross "halfopen" 3)
(chinesecymbal laThin #f 5)))
%- test
\new DrumStaff
<<
\set DrumStaff.drumStyleTable = #(alist->hash-table my-drums)
\customChineseCymbalNoteHead
\drummode {
\textLengthOn
hhho1^"halfopenhihat "
hhho2
hhho4
hhho8
hhho16
hhho32
hhho
cymch1^"chinesecymbal"
cymch2
cymch4
cymch8
cymch16
cymch32
cymch
}
>>
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics and polyphony
Hello,
On 4 January 2012 22:50, Xavier Scheuer wrote:
> On 4 January 2012 23:32, Carl Sorensen wrote:
>>
>> Please see the Notation Reference, section 1.5.2. In particular, look at
>> Temporary polyphonic passages.
>
> This problem pops up often. I remember having replied to dozens of e-mails
> —both on the French users mailing list and on lilypond-user— from
> confused users about this. This is indeed explained in the notation
> reference that
>
> "[The << {...} \\ {...} >> construct] behaves differently to the
> similar construct without the double backslashes: all the expressions
> within this construct are assigned to new Voice contexts."
>
> but could it be added that this implies the (dynamic) spanners, lyrics
> associated to voice, etc. cannot be used from outside to inside the
> << {...} \\ {...} >> construct (and vice versa)?
> And would it be possible to put a "warning box" or so around this?
> Maybe we could add also a similar warning in the learning manual,
> LM 3.2.1 I’m hearing Voices.
>
> What do you think? James?
For now I've created
http://code.google.com/p/lilypond/issues/detail?id=2179
Regards
--
--
James
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bug squad - updated list
Hello,
On 2 January 2012 22:38, -Eluze wrote:
>
>
> Graham Percival-3 wrote:
...
>>
>> Eluze, could you suggest a change to the wording in the CG to
>> clarify this point? Either James or Phil could push that directly
>> to staging.
>>
> maybe something like:
>
> you will automatically be considered/treated as stared if you enter a new
> issue.
>
>
> and:
> if you want to be acknowledged when other issues are changed you must star
> them yourself (otherwise they will only appear in the bug-ignore or
> bug-current folder)
>
> is this correct and does this make it clearer?
I think so. However as Phil is the Bug squad Meister, I've attached
the patch here that he can check and push if it is correct.
regards
--
--
James
From 3c1f6449f20c5c3f8acf209c25fee6fcd6f88b63 Mon Sep 17 00:00:00 2001
From: James Lowe
Date: Thu, 5 Jan 2012 06:29:42 +
Subject: [PATCH] Doc: CG Add note for Bug-Squad issues
Requested by Eluze.
Added note on how to make sure that you receive any emails when a Tracker
issue is updated.
---
Documentation/contributor/issues.itexi |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 86976fd..be5ac5a 100644
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -759,6 +759,10 @@ was sent to multiple mailing lists (such as both @code{user} and
@code{bugs}), then reply to all those mailing lists as well. The
email should contain a link to the issue you just added.
+@warning{If you wish to be notified on any Tracker issue that you or
+anyone else have created, then either star the issue or add your email
+address to the @code{CC} of the Tracker issue.}
+
@end enumerate
--
1.7.0.4
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
