From: P Levine <plevine457@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dolphin only allowing a single instance after update
Date: Thu, 22 Aug 2019 19:00:54 -0400 [thread overview]
Message-ID: <CADX8ZBK_ACfmECvmMw9WbDhgnFVGWSvZ=u-N0QAGPV00BriQ=w@mail.gmail.com> (raw)
In-Reply-To: <914516a1-039a-8194-d8af-73e1fcde2cb4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On Fri, Aug 16, 2019 at 10:56 PM Dale <rdalek1967@gmail.com> wrote:
> Howdy,
>
> I upgraded my system last night. I logged out and back in earlier and
> have noticed something new. It seems to only allow one instance of
> Dolphin to run at a time. I usually have three or four running for
> doing different things in different locations. It just makes it easier
> for me to multi-task at times. What I've noticed with the new version
> is that if I have a instance open on say desktop 7 and then want to open
> a new instance on desktop 4, it moves the already running dolphin from
> desktop 7 to 4. It doesn't open a new instance. I then lose where I am
> when I get ready to go back to work on something in the previous instance.
>
> Current version of Dolphin and USE flags:
>
> kde-apps/dolphin-19.08.0:5::gentoo USE="handbook -activities -debug
> -semantic-desktop -test"
>
> Previous version that worked normally:
>
> kde-apps/dolphin-19.04.3
>
> Has anyone else noticed this? I've looked in the Configure section to
> see if I can change the behavior but can't find anything related. I
> checked to see if I could add a option on the command line as well. I
> even poked around System Settings but can't find anything there either.
> Is this a new thing, a bug or what?
>
> Thanks for the help.
>
> Dale
>
> :-) :-)
>
The behaviour was changed such that dolphin opens new instances in tabs by
default. If you want to change that, edit the desktop file and add the
*--new-window* option to the command.
[-- Attachment #2: Type: text/html, Size: 2295 bytes --]
next prev parent reply other threads:[~2019-08-22 23:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 2:56 [gentoo-user] Dolphin only allowing a single instance after update Dale
2019-08-17 20:46 ` Philip Webb
2019-08-17 23:48 ` Dale
2019-08-18 0:17 ` Philip Webb
2019-08-18 2:31 ` Dale
2019-08-18 1:25 ` Daniel Frey
2019-08-18 2:36 ` Dale
2019-08-18 18:53 ` [gentoo-user] " Nikos Chantziaras
2019-08-18 21:57 ` Dale
2019-08-18 22:51 ` Mick
2019-08-19 3:56 ` Dale
2019-08-22 23:00 ` P Levine [this message]
2019-08-22 23:56 ` [gentoo-user] " Dale
[not found] ` <20280.1566522215@owl.pooh.corner>
2019-08-23 1:16 ` Dale
2019-08-23 2:16 ` P Levine
2019-08-23 4:56 ` Dale
2019-08-23 6:27 ` P Levine
2019-08-23 9:32 ` Dale
2019-08-23 8:18 ` Mick
2019-08-23 8:27 ` [gentoo-user] " Nikos Chantziaras
2019-08-23 10:33 ` Mick
2019-08-23 9:49 ` [gentoo-user] " Dale
2019-08-23 10:29 ` Franz Fellner
2019-08-23 11:05 ` Dale
2019-08-24 7:16 ` Thomas Mueller
2020-03-26 5:15 ` J. Roeleveld
2020-03-26 6:46 ` Dale
2020-03-26 7:23 ` J. Roeleveld
2020-03-26 8:47 ` Dale
2020-03-26 9:03 ` Peter Humphrey
2020-03-26 9:28 ` Dale
2020-03-26 9:49 ` J. Roeleveld
2020-03-26 9:58 ` J. Roeleveld
2020-03-26 9:46 ` J. Roeleveld
2020-03-28 14:43 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADX8ZBK_ACfmECvmMw9WbDhgnFVGWSvZ=u-N0QAGPV00BriQ=w@mail.gmail.com' \
--to=plevine457@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox