Removing the detaching and KDEV_SESSION

[David Nolden]

Am Sonntag 31 Januar 2010 22:53:12 schrieb Andreas Pakulat:
> Reasoning: Its impossible by now to let users easily fetch the debug
> output of kdevelop and add it to a bugreport. They have to jump through
> hoops to do that as normal stdout-redirection doesn't work anymore. This
> just adds yet another problem on top of the existing ones. And at this
> point I value these problems higher than separating the duchain data.

Sorry I misunderstood the last message.

This is stupid. We can simply add a "--nofork" option and be ready, it would 
solve both the debugging- and the debug-output problem. It doesn't matter 
whether you tell a user to do "kdevelop > ./output" or "kdevelop --nofork > 
./output". That option will cost only 5 lines of code.

Yes, it will use another .kdevduchain dir with the --nofork option, but that 
simply doesn't matter, because the duchain dir is wiped anyway after 2 
crashes.

And I find it annoying that this subject is brought up again and again. 
Changing anything about that is out of discussion in medium-term, as the 
relation between effort and potential value is exorbitantly bad.

Greetings, David