Re: Crash with simultaneous-duplicating music function and \once\offset

2018-07-17 Thread Simon Albrecht
On 17.07.2018 20:46, David Kastrup wrote: I got Tracker issue: 5386 (https://sourceforge.net/p/testlilyissues/issues/5386/) Rietveld issue: 367760043 (https://codereview.appspot.com/367760043) Issue description: Make grob-transform robust against cloned invocations Well, "robust" is a bit

Re: Crash with simultaneous-duplicating music function and \once\offset

2018-07-17 Thread David Kastrup
Aaron Hill writes: > On 2018-07-17 11:46, David Kastrup wrote: >> Aaron Hill writes: >>> I tried manually duplicating the music: >>> >>> >>> \version "2.19.82" >>> music = { \once \offset length 5 Stem c'4 c'4 } >>> musicCopy = { \once \offset length 5 Stem c'4 c'4 } >>> \new Staff

Re: Crash with simultaneous-duplicating music function and \once\offset

2018-07-17 Thread Aaron Hill
On 2018-07-17 11:46, David Kastrup wrote: Aaron Hill writes: I tried manually duplicating the music: \version "2.19.82" music = { \once \offset length 5 Stem c'4 c'4 } musicCopy = { \once \offset length 5 Stem c'4 c'4 } \new Staff { c'4 << \music \musicCopy >> c'4 } This var

Re: Crash with simultaneous-duplicating music function and \once\offset

2018-07-17 Thread David Kastrup
Aaron Hill writes: > On 2018-07-15 20:09, Aaron Hill wrote: >> Seems the custom music function is not needed to reproduce a crash. >> >> >> \version "2.19.82" >> music = { \once \offset length 5 Stem 4 4 } >> << \music \music >> >> >> >> This also results in: >> >>> GNU LilyPond 2

Re: [BUG] Problems in gregorian style lyrics with combination of episem and melisma

2018-07-17 Thread David Kastrup
"James Lowe" writes: > Hello, > > On Sun, 15 Jul 2018 08:59:01 +0200, "Jaap de Wolff" wrote: > >> Hello, >> >> About a week ago I did sent the bug report below. >> There was a comment on it on which I replied. >> At this moment it is still not on the bug list, while younger reports are. >> No o

Re: [BUG] Problems in gregorian style lyrics with combination of episem and melisma

2018-07-17 Thread James Lowe
Hello, On Sun, 15 Jul 2018 08:59:01 +0200, "Jaap de Wolff" wrote: > Hello, > > About a week ago I did sent the bug report below. > There was a comment on it on which I replied. > At this moment it is still not on the bug list, while younger reports are. > No one told me it was not a proper bug

Re: TimeSignature and magnifyStaff

2018-07-17 Thread James Lowe
Hello, On Tue, 17 Jul 2018 06:05:13 -0700 (MST), foxfanfare wrote: > As a new LilyPond user, I never opened an issue for signaling a bug. Could > someone please do it, or explain me how to proceed? Thx We're still establishing if it is a bug or an enhancement (see thread). However, for now I h

Re: TimeSignature and magnifyStaff

2018-07-17 Thread Karlin High
On 7/17/2018 8:05 AM, foxfanfare wrote: or explain me how to proceed? Have you already reviewed the LilyPond website's bug report instructions? Or, for in-depth instructions for regular contributors, try the Contributor Guide's chapter 8, "Issues."

Re: TimeSignature and magnifyStaff

2018-07-17 Thread foxfanfare
As a new LilyPond user, I never opened an issue for signaling a bug. Could someone please do it, or explain me how to proceed? Thx -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ bug-lilypond mailing list bug-lilypond@gnu.org