Console plugin significantly slows down build process
Submitted by on Sunday, 19 November, 2006 - 11:59
Hi,
I've started using the Console plugin (with the ErrorList plugin) to build our project. First, I must say that the Console plugin is really great - it is very easy to configure to support other tools (e.g. g++), and it simplies working with jEdit a lot.
The problem is that the output of my build process, which is quite large, is displayed in the Console plugin very slowly (much slower than the Linux shell), and this slows down the build significantly. Any idea why this happens or what I can do to fix this slowdown?
Also, from the documentation of the Console plugin, it seems like it tries to match all the Error Patterns until it finds a match. Is this the way it works? While it may be good enough for most purposes, there are several problems with this:
1. Lines which do not express errors in the output of one tool, may express errors in the output of another tool. So if I'm running the first tool, I may get false errors because its output is also matches with the other error patterns. (Probably rare, though)
2. The output is probably slowed down by several redundant pattern matches.
Since the Console plugin cannot really know which tool is generating the output, it can either try all of the Error Patterns or rely on the user to indicate which Error Patterns to include. When I run "make", I only have "g++" output, so I don't need to match all other patterns (I've added a 'g++' error pattern manually). When I run Perl, I only have Perl output. I can erase some error patterns to exclude them, but I think the Console plugin should enable the user to select the active error patterns to use (e.g. using check-boxes or using disable/enable buttons below the Error Patterns list), to avoid unwanted pattern matches.
Shlomy
I've started using the Console plugin (with the ErrorList plugin) to build our project. First, I must say that the Console plugin is really great - it is very easy to configure to support other tools (e.g. g++), and it simplies working with jEdit a lot.
The problem is that the output of my build process, which is quite large, is displayed in the Console plugin very slowly (much slower than the Linux shell), and this slows down the build significantly. Any idea why this happens or what I can do to fix this slowdown?
Also, from the documentation of the Console plugin, it seems like it tries to match all the Error Patterns until it finds a match. Is this the way it works? While it may be good enough for most purposes, there are several problems with this:
1. Lines which do not express errors in the output of one tool, may express errors in the output of another tool. So if I'm running the first tool, I may get false errors because its output is also matches with the other error patterns. (Probably rare, though)
2. The output is probably slowed down by several redundant pattern matches.
Since the Console plugin cannot really know which tool is generating the output, it can either try all of the Error Patterns or rely on the user to indicate which Error Patterns to include. When I run "make", I only have "g++" output, so I don't need to match all other patterns (I've added a 'g++' error pattern manually). When I run Perl, I only have Perl output. I can erase some error patterns to exclude them, but I think the Console plugin should enable the user to select the active error patterns to use (e.g. using check-boxes or using disable/enable buttons below the Error Patterns list), to avoid unwanted pattern matches.
Shlomy
