IIRC we recently removed some of the filtering from the make output as it was getting really slow for lots of output. svn log on parts/outputviews/ should show you the commit.

All the filtering logic is in that directory.

Is there a unit test for the Messages outputview.

I assume KDevelop forks the child make process and then reads in the stdout and stderr which are produced.

Therefore to test this, the make could be replaced with an invocation of a simple script which produces various messages on stdout and stderr.

I often build systems with very noisy output. KDevelop is great with its “Very short compiler output” mode.

Without this warnings got buried in thousands of lines of informational text. Therefore it’s a strong reason for people to use this IDE instead of the command line.

Some time between KDevelop 3.5.0 and 3.5.1, the behaviour of “Very short compiler output” changed and it no longer condenses the output as efficiently as it did before (for my build at least).

Since “very short” is a matter of opinion, do you have a set of rules against which this feature should operate?

With a set of requirements we could then have tests to ensure we don’t get regressions from previous releases.

If these exist already, could you point out where they are.

I’d like to fix this so any help is appreciated. It’s also good to know that KDevelop3 is still open for fixes.

Thanks,
Paul