>> OK, to debug further can you please run this using the latest GIT code:
>> valgrind --tool=callgrind kmail --nofork immediately exit kmail, and
>> send me the generated
>> callgrind.out.<pid> file?  I can then use that file to analyze the
>> execution of the code on your machine and see if there is another
>> suboptimal codepath
>> in use.
>>
>> At least the numbers are now generally within 1/2 second of the original
>> numbers...
>
> kmail:
> http://humanreadable.nfshost.com/trinity/build_logs/callgrind.out.574
>
> konqueror:
> http://humanreadable.nfshost.com/trinity/build_logs/callgrind.out.19425
>
> kate:
> http://humanreadable.nfshost.com/trinity/build_logs/callgrind.out.21982
>
> Darrell

Thank you for the callgrind logs.  I have pushed a patchset into GIT that
should speed things up considerably, however the style API/ABI broke as a
result, so you will need to recompile TQt3, tdelibs,tdebase, tdeartwork,
and the tde-style-* applications.

Tim