Kdevelop for console application development - a few questions

[Milian Wolff]

On Tuesday 24 April 2012 16:17:45 David Nolden wrote:
> I think the solution here is an improved integration of the integrated
> konsole toolviews.
> 
> What we need is a konsole-command "dbg! path_to_app" which would run
> the application right in the toolview, but attach kdevelop as a
> debugger.
> 
> When debugging is started from the GUI we can simply send "dbg!
> path_to_app" to an integrated konsole to forward the output right
> there.
> 
> Furthermore, the environment of the konsole toolview (see integrated
> "setenv!" command) should be set to "debug", and the environment
> attached to a toolview should be shown in its title.
> 
> The effect would be, that the output of debugged applications would be
> shown in an editable toolview with the title "Konsole: debug".
> 
> I might implement both of these at some point, starting with the second.

Nice but keep in mind that while your work on this is nice for many, there 
just as many that do not use Bash and hence cannot apply your bashisms to 
their shell of choice... Could we maybe abstract it in a way to make it 
possible to use it also from other shell implementations (zsh being the most 
famous one I guess)?

bye

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20120424/cf78ed14/attachment.sig>