|
From: Slava P. <sl...@je...> - 2001-08-19 08:01:01
|
On Thu, Aug 16, 2001 at 02:21:06PM -0400, John Gellene wrote: > One solution might be for the error parser to maintain state between lines > of parsed output. You could specify text patterns for ERROR, ERROR_DATA, > SUB_ERROR and END_ERROR. You would have to link error patterns more closely > with particular programs; they would become more like syntax highlighting > modes in their complexity and accessibility. I think ultimately a set of > error patterns should be associated with a project, as an adjunct of the > tool or tools that the project uses. Sounds more and more like an IDE to > me. I think this is the best solution. I will try and implement it in Console 3.0, or maybe a subsequent release. > A more immediate and less ambitious fix might involve two things: > > (1) Make error sorting by file name optional. I question whether file > sorting in a tree as opposed to a linear list is really that useful to > anyone, but providing this option makes that discussion academic. This is harder than your first suggestion. > (2) Make another option that would cause all non-blank lines of text > following a error pattern hit to be part of the same leaf node until the > next hit occurs or end of stream is reached. This may end up being a little > overinclusive in writing leaf node text, even after some tweaking and > hacking. It would still be a lot more useful. I don't like this one either; it would add too much junk that is not actually part of the error message to errors. Slava |