[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 208854] run tag shows one output whereas konsole output shows
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2009-09-30 10:46:16
Message-ID: 20090930104617.0DAC72223F () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=208854





--- Comment #7 from Andreas Pakulat <apaku gmx de>  2009-09-30 12:46:12 ---
(In reply to comment #6)
> It would be better though if we showed the same output as konsole.

We actually do show the same output (minus any colors, which can be added
relatively easily). 

> After all, KDevelop will look broken when this happens, no matter what the technical reason is.
> 
> Maybe we can take a look at what konsole does differently..

I'm not an expert on terminal emulators, but I think thats the reason konsole
has no buffer, while KDevelop has. We're getting the process output via a pipe,
while I think konsole gets that output in a different way. And the OS simply
doesn't buffer the pseudo terminal that Konsole uses.

I don't think its useful to spend time on trying to find a way of "working
around" the OS. Its a well known fact that you won't see stdout output directly
until you use fflush().

Oh, another thing is that we actually do need to wait for the line-end
character as we cannot convert the given byte array into a QString without
knowing the line is done. Else we might have received only part of a multi-byte
sequence.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]