(*** This bug was imported into bugs.kde.org ***) Package: konqueror Version: 2.1.1 (using KDE 2.1.1 ) Severity: wishlist Installed from: Linux-Mandrake 8.0 i586 Compiler: gcc version 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk) OS: Linux 2.4.2-11mdksmp i686 OS/Compiler notes: I wish konqueror had an "open in new process" entry in the context menu of a link that would make it fork() a new process with that URL. I also wish there was an option to make this the default behaviour for a middle button click as it would make the browser more robust. (Submitted via bugs.kde.org) (Called from KBugReport dialog)
On Sunday 06 May 2001 02:33 rprior@inescporto.pt wrote: > Package: konqueror > Version: 2.1.1 (using KDE 2.1.1 ) > Severity: wishlist > Installed from: Linux-Mandrake 8.0 i586 > Compiler: gcc version 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk) > OS: Linux 2.4.2-11mdksmp i686 > OS/Compiler notes: > > I wish konqueror had an "open in new process" entry in the context menu of a link that would make it fork() a new process with that URL. I also wish there was an option to make this the default behaviour for a middle button click as it would make the browser more robust. Update to kde-2.2-alpha1 there is a kcontrol setting for when to create a new process and when not to. -- David FAURE david@mandrakesoft.com faure@kde.org http://perso.mandrakesoft.com/~david/ http://www.konqueror.org/ KDE Making The Future of Computing Available Today
Rather an old wish...but has this kcontrol disappeared in 3.2.x? I tried to set the mentioned behaviour on my 3.2.2 but wasn't able to find the setting. The problem here is that I'll lose all my konqueror windows if one instance of these child-processes hangs and has to be killed (happened last yesterday: I tried to print a web page, this didn't work, instead all konqueror windows derived from the same mother process hang and disappeared when I killed the non-printing window).