I propose narrowing the definition of "Crash" to abnormal termination by
the OS and relabeling issues of the latter two kinds as "Defect".
+1 in general. Scheme errors, if it's in LilyPond's Scheme code, may
qualify as well IMO, if the input is "well-formed" (ie no wrong user
Scheme code).
I was annoyed the last time I was in the mood to work on segfaults and
had to sift through a bunch of Scheme exceptions to find them. That's
why I want to move them out of "Crash".
I could create a new label ("Error" or whatever you'd prefer) for
non-crash error handling: false positives, false negatives, confusing
messages, etc. I'm not a fan of having many labels, but if people would
want to search for such issues in a category apart from "Defect", then
it would be useful.
If you think it's useful, also consider changing the label description.
Thanks. I plan to.
--
Dan
