On Sat, 2013-12-21 at 11:58 -0600, Jeremiah Benham wrote: > > On Dec 21, 2013 9:49 AM, "Richard Shann" <[email protected]> > wrote: > > > > On Sat, 2013-12-21 at 09:41 -0600, Jeremiah Benham wrote: > > > Here is some more info.... > > > I turned off window decorations and the problems were still there. > > > They were a bit worse because I could not kill the window to force > the > > > refresh. I turned off continuous typesetting and then clicked on > > > refresh in the printview window but nothing appeared to happen. If > > > window decorations were on I could kill the window to force the > > > refresh. I monitored the date/time on the files in /tmp and both > > > the .ly and .pdf updated when I clicked refresh. Nothing updated > in > > > evince. With window decoration off I had to hit refresh again. > Then a > > > popup popped up (behind the evince window) asking me to kill the > > > current print job. I clicked yes. Then evince refreshes. > > > > This all sounds consistent with the child_watch never seeing the pid > > die. You could write a very crude work around that would keep > checking > > for the print job finishing ... does the top or ps command show that > the > > LilyPond process does actually finish and not go zombie or > something? > > > > Good call! I see the lilypond was running even after 30min. Once I > killed lillypond evince refreshed. Why does lilypond exit correctly > with export pdf but not printview refresh?
There is an official LilyPond installer I guess, if you install that and point Denemo to use it does that work? And does the Denemo installed LilyPond terminate if run externally? And what is the difference in the arguments array and/or the g_spawn_ call when the lilypond is spawned for Export PDF? Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
