Re: Issue 38 in lilypond: collision fingering beam

2009-11-26 Thread lilypond
Updates: Owner: percival.music.ca Comment #5 on issue 38 by jameseli...@googlemail.com: collision fingering beam http://code.google.com/p/lilypond/issues/detail?id=38 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fiel

Re: Issue 38 in lilypond: collision fingering beam

2009-11-26 Thread lilypond
Updates: Status: Verified Owner: --- Comment #4 on issue 38 by jameseli...@googlemail.com: collision fingering beam http://code.google.com/p/lilypond/issues/detail?id=38 (No comment was entered for this change.) -- You received this message because you are listed in the owner

Re: Issue 38 in lilypond: collision fingering beam

2008-11-19 Thread Trevor Daniels
MAIL PROTECTED]>; Sent: Wednesday, November 19, 2008 5:53 AM Subject: Re: Issue 38 in lilypond: collision fingering beam From: Trevor Daniels I've added a snippet based on the example supplied by Mark Thanks Mark Credit should go to Eluze for the example menti

Re: Issue 38 in lilypond: collision fingering beam

2008-11-18 Thread Mark Polesky
From: Trevor Daniels > I've added a snippet based on the example supplied by Mark > Thanks Mark Credit should go to Eluze for the example mentioned. I had nothing to do with it. - Mark ___ bug-lilypond mailing list bug-lilypond@gnu.org http:/

Re: Issue 38 in lilypond: collision fingering beam

2008-11-18 Thread Eluze
who's who? Trevor Daniels wrote: > > I've added a snippet based on the example supplied by Mark > to the repository in a form which is suitable for inclusion > in the selected snippets section of NR 1.7 Editorial annotations. > It will appear in the docs in due course. > > See Avoiding collisi

Re: Issue 38 in lilypond: collision fingering beam

2008-11-18 Thread Trevor Daniels
I've added a snippet based on the example supplied by Mark to the repository in a form which is suitable for inclusion in the selected snippets section of NR 1.7 Editorial annotations. It will appear in the docs in due course. See Avoiding collisions of chord fingering with beams Thanks Mark Tr

Re: Issue 38 in lilypond: collision fingering beam

2008-11-16 Thread Eluze
codesite-noreply wrote: > > Issue 38: collision fingering beam > http://code.google.com/p/lilypond/issues/detail?id=38 > > Comment #2 by n.puttock: > This is invalid. > i don't really understand what is invalid - there is a collision, it is not readable and it is not what we are used from liy

Issue 38 in lilypond: collision fingering beam

2008-11-07 Thread codesite-noreply
Issue 38: collision fingering beam http://code.google.com/p/lilypond/issues/detail?id=38 Comment #3 by v.villenave: OK thx. Issue attribute updates: Status: Invalid -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this

Issue 38 in lilypond: collision fingering beam

2008-11-07 Thread codesite-noreply
Issue 38: collision fingering beam http://code.google.com/p/lilypond/issues/detail?id=38 Comment #2 by n.puttock: This is invalid. Stems are deliberately excluded from the supports of fingerings inside chords unless 'add-stem-support = ##t. -- You received this message because you are list

Issue 38 in lilypond: collision fingering beam

2008-05-30 Thread codesite-noreply
Issue 38: collision fingering beam http://code.google.com/p/lilypond/issues/detail?id=38 Comment #1 by v.villenave: (Reproduced with 2.11.47) It does only affect chords indeed. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred t