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

List:       kdevelop-bugs
Subject:    [Bug 232865] console output slow and we can't copy multiple lines to
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2010-04-01 0:22:08
Message-ID: 20100401002208.9BE473C630 () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #10 from Andreas Pakulat <apaku gmx de>  2010-04-01 02:22:02 ---
(In reply to comment #9)
> (In reply to comment #8)
> > Don't bother, its already filed as wish (search for kdevplatform/outputview).
> 
> Thx.
> 
> Concerning the output windows, wouldn't it be possible to use libkonsolepart
> only for the debug output? because I think we don't need interactions with the
> text in this case. Also this would solve the text copy pb..

Certainly not for debug. Konsolepart is not something which you can use as
"output", all you can do is start some application in it. And thats it, you
can't even communicate with that app, which we need for the debug-case as we
need to talk to gdb.

And even for the app-output it doesn't make sense as we then have no way
anymore to kill the application when the user hits the stop button.

Using konsolepart means completely giving up any control, which is not
acceptable for running or debugging the application.

-- 
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]