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

List:       kdevelop-bugs
Subject:    [Bug 146194] open documents from built-in konsole
From:       David Nolden <david.nolden.kdevelop () art-master ! de>
Date:       2007-05-31 16:56:45
Message-ID: 20070531165645.4921.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=146194         




------- Additional Comments From david.nolden.kdevelop art-master de  2007-05-31 \
18:56 ------- It's a fact that many people are familiar with the console, and use it \
a lot. I am one of them. 

Maybe the reason is that kdevelop really has some limitations, but we cannot expect \
kdevelop-4 to be perfect from the beginning, and even if would be perfect I'd \
probably still sometimes use the console, it's simply more versatile than any IDE can \
ever be(though an IDE is more comfortable).

I'd also like kdevelop to be usable on projects that are not imported into kdevelop, \
as a utility that makes a programmers life easier, without forcing him to setup a \
project before he wants to change just a line of code and compile.

Just think how easy this would be:
svn checkout https://someIntersetingNonKdeProject
cd trunk
open buggyFile.cpp  
#edit a few lines to support your hardware or something
make  
#get the output parsed by kdevelop, jump to your syntax-error using f4, repair it
make 
#ready

That's so comfortable, even a console-hacker would love it. :)

Now think how much work it would be doing this with kdevelop-3.4. You'd probably \
prefer kate for doing it.

So I think such commands would be very useful, and given how easy that would be to \
implement with the right dbus interfaces in place, I don't know why we shouldn't do \
it.


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