Hi Carl, Have not tried that idea.
The weird thing is that it's only dynamics that are affected. I thought it might be some subtle font caching issue with the font I use, but I reverted to lilypond default and the same occurs. Once the dynamic finally makes itself visible, it stays. This may remain forever an unsolved mystery. But it makes Frescobaldi currently unusable for me, espcially as I am in the 'add dynamics' phase that I do. I have several decades of UNIX software development experience, and I have never seen anything resembling this. I promise I am not making it up! Andrew On Wed, 14 Nov 2018 at 05:08, Carl Sorensen <c_soren...@byu.edu> wrote: > Have you tried changing the lilypond call in Frescobaldi to a gdb lilypond > call, so that you can pause the execution of lilypond and give Frescobaldi > time to do whatever it might do -- and then continue lilypond from the > debugger? > > Have you tried changing the Frescobaldi options for displaying the pdf to > get to a minimal Frescobaldi run that doesn't do much but generate the pdf? > > This sounds like a truly bizarre bug. > > _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
