On April 23, 2018 at 4:24 AM Richard Shann <rich...@rshann.plus.com> wrote:
On Sun, 2018-04-22 at 19:30 -0400, Bric wrote:On April 21, 2018 at 8:53 PM Bric <b...@flight.us> wrote:The following extra detail could be relevant to your development and
[...]
tweaking, though i'm not 100% sure it's a denemo "mis-behavioral":
It crashed on me twice on lilypond syntax error, during Print View
refresh.
"It crashed"? what did? what were the symptoms?
Hi. Started replying several days ago, then system froze and I didn't have time to try to reconstruct what I had written.
At this point I don't remember, but it's mostly what i wrote earlier, plus some extra observations:
Denemo has triggered session crash of my (apparently less than stable Ubuntu), in particular operations, though i'm not even sure if they can be put under some common umbrella (not knowing the nuts & bolts) :
1) Refreshing Print View (and maybe Playback view as well... can't remember for sure). Often when there are lilypond syntax errors, but not always.
2) On first run of the application after a crash, and attempting to use or just to open the Print View (when it starts refreshing itself, i suppose).
3) On saving a lilypond export, when I hit "Save" in the file dialogue
I don't remember any crashes while using just the editor (inputing, editing, saving there).
I may not be remembering a few other potentially useful details; sorry - might update later.
So, I'm actually getting stuff done using Denemo, but with the occasional crash interruptions (I make sure to hit "Ctrl+S" a LOT)
There is a purple error message in the preview window, at the top,saying the cursor was probably placed where the error is, in the
editor.
That means that the LilyPond process emitted some error or warning
message with a line and column reference to the LilyPond syntax, which
Denemo then tried to tie back to the place in the Denemo Display
("editor") which corresponded to that bit of syntax. This fails if the
line/col reference is not to something inside the music but in the
headers etc.My particular syntax errors were tying two notes [...] which were not
the same pitches [...]
This will not cause LilyPond any problem (it happens a lot while
editing), LilyPond will issue a warning (and hence Denemo will try to
position the cursor) and not draw a tie.i THINK i've seen it crash before on lilypond syntax...
You can get LilyPond to crash on syntax, but it would not be able to
cause Denemo to crash, they are completely different Unix processes -
if your O/S or hardware is faulty it might cause a system crash...
All that Denemo is doing is its usual cycling round waiting for the O/S
to signal that the LilyPond process has terminated (and, in that case
what it said) or if you have pressed a key or clicked a mouse or played
on your MIDI controller. It's doing that all the time, so unless the
LilyPond process blew the whole system up there is nothing special
going on.
The worst that can happen is the LilyPond hangs and then Denemo
continues waiting for it to finish. You can kill the LilyPond off via
the progress bar and/or by starting another typeset.
Richard
_______________________________________________
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel
_______________________________________________ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
