Removing the detaching and KDEV_SESSION

[Milian Wolff]

Niko Sams, 01.02.2010:
> On Mon, Feb 1, 2010 at 00:55, David Nolden <zwabel at googlemail.com> wrote:
> > Am Montag 01 Februar 2010 00:48:57 schrieb Niko Sams:
> >> On Mon, Feb 1, 2010 at 00:44, David Nolden <zwabel at googlemail.com> wrote:
> >> > 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.
> >> 
> >> If this is possible - why don't we do it always?
> >> What is the problem with multiple sessions in one duchain repository?
> > 
> > The problem is that, when you have multiple sessions open at the same
> > time, they would be randomly distributed over different duchain
> > repositories.
> 
> Is it that common to have more than two instances open at the same time?
> And what is the problem with two or three repositories?
> 
> My usecase:
> - xdebug-session: xdebug, executebrowser, kdevplatform
> - kdevelop-session: kdevelop, kdevplatform
> - php-session: php, kdevplatform
> - css-session: css, kdevplatform
> 
> at work I have similar sessions, each containing 3 large libraries and
> the (relatively small) webproject itself.
> 
> so for me even with session separated repositories it's the same problem.

Imo the problem is: Multiple KDev instances _could_ open one and the same 
session. Esp. when you have two different sessions opened and restart KDE, one 
and the same session will be reopened twice.
-- 
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: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100201/4ea5898b/attachment.sig>