[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Solved] buster: multiple instances of konqueror?



D. R. Evans, on 2019-09-05:
> Étienne Mollier wrote on 9/5/19 1:38 PM:
> > 	$ konqueror . # brings up a new window showing the CWD
>
> If I map "alt-S" to "konqueror <my-home-directory>" instead of just
> "konqueror" then it seems perfectly happy to start multiple instances.
>
> So the problem is solved -- if not understood -- and I thank you for this clue.

You are welcome, I hope you won't mind if I append a little
"[Solved]" marker in the "Subject:" field in that case.  :)


[... rewinding ...]
> > On my side, the window manager happily brings up the first
> > konqueror window having been started, and the "konqueror"
> > command gives back the hand to the shell, instead of spawning a
> > new window, which I believe is the expected behaviour ?
>
> I'm afraid that I don't understand what you are asking.

Nevermind, I was merely wondering what was the behaviour you
were expecting "physically" on your screen.  I supposed you
wanted to spawn new windows, but was not sure 100%.  Given your
new "alt-S" key binding, I tend to believe I hit bull's eye
(although we're still talking about Buster.  ;)

> > According to my few tests and browsing diverse konqueror related
> > documents, it would seem that running several konqueror
> > processes is technically prevented by various means, probably
> > on purpose.
>
> I wonder why? [...]

That is an hypothesis, I am not a kdevelopper at all, but having
a single process, a single entry point, for doing desktop
integration tasks, for instance receiving a request for opening
a PDF, is probably easier when you know in advance where to put
your PDF opening request to.

There is the DESIGN file at the root of konqueror source code,
giving an overview of the way the program functions and
interacts with other parts of the system (the file is dated from
2007, but I suppose the idea remains).  The program kfclient is
a command you can use to open almost any file, and it tries to
connect to existing running konqueror processes when it exists.
This change of behaviour /might/ be a side effect of that
general policy.

> I've used konqueror since the old Mandrake days (somewhere around 2002 is my
> best guess). Multiple instances have always worked fine before on my systems.
> I find the change very mysterious... and the lack of documentation anywhere I
> can find to justify, or even describe this new behaviour, equally puzzling.

Cool, I started with GNU/Linux with the later version Mandriva
2007, when I was a teenager, and did work a bit with konqueror,
on KDE 3.5.  I /only/ begun using Debian with Lenny, but I
digress.

Kind Regards,  :)
-- 
Étienne Mollier <etienne.mollier@mailoo.org>
Fingerprint:  5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d


Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: