Usually it happens that I end up with multiple instances of Dolphin when all I need is a single Dolphin instance, having multiple instances of Dolphin is kind useless with Dolphin supporting tabbed browsing; there's still some cases when I need two or more instances of Dolphin at the same time but that's not very frequent.


Reproducible: Always

Steps to Reproduce:
1. Launch Dolphin.
2. Launch Dolphin again.
3.
Actual Results:  
Multiple instances of Dolphin will pop up.

For example:
1. if I open Dolphin in a particular directory from the console it will spawn a new Dolphin session instead bringing up the already running session showing the directory's content on the main window - or in a new tab, that would be a nice feature too.
2. If I choose to open a file location (while using a web browser or any other application) that will spaw another instance o Dolphin instead reusing the already running Dolphin.


Expected Results:  
Have an option to control how Dolphin instances are spawned. The ideal feature-set for Dolphin's instance spawning behaviour would be:
1. Let the user spawns at much parallel instances as he/she wants/needs.
2. Let the user use only one instance of Dolphin redirecting every other Dolphin calls to the main Dolphin window - one can allways use Back button if need to access previous location.
3. Open a new tab in the current Dolphin window instead spawning multiple instances.
As you see the Dolphin behaviour and workflow I'm looking for is like actual web browsers have.

Say I have multiple ways to access Dolphin - actually don't albeit it's good use case example: suppose I can launch Dolphin from the panel dock, from Kickoff (or Lancelot or whatever else) and from a plasmoid (or a desktop link). Every time I click on one of the icons I will have a new Dolphin instance instead pushing the already running instance to the front and showing the default directory in the main window or creating a new tab with the default location.