https://bugs.kde.org/show_bug.cgi?id=447394
Toni Asensi Esteve <toni.ase...@kdemail.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Regression: New Tab actions |New Tab actions perform a
|perform a tab duplication |tab duplication instead of
|instead of opening a fresh |opening a fresh tab
|tab |
Ever confirmed|1 |0
Status|CONFIRMED |REPORTED
--- Comment #2 from Toni Asensi Esteve <toni.ase...@kdemail.net> ---
If someone follows the development of Krusader he/she can see that there's a
commit "New tabs start in the current folder and can be inserted next to the
current tab or at the end", with its merge request.
As it's already explained in the aforementioned merge request :
The aforementioned programs (Konsole, Double Commander, Total Commander or
Dolphin) do that, so people who use those programs are used to the fact that
when they open a new tab, it starts from the same folder that they were using.
When trying Krusader, they do not expect that new tabs start from the home
folder.
If the user is working on a folder, it's more frequent that the next action is
going to be done in that folder or near it (a subdirectory, upper directory,
etc.) instead of in the home folder. Anyway, going to the home folder is easy
with a hotkey (Alt+Home) or using a Krusader button that can be enabled.
That change is not a regression since is a design decision, intentional,
approved and Krusader developers, people who use the git version, and users of
e.g. the [PPA of Rik
Mills](https://launchpad.net/~rikmills/+archive/ubuntu/experimental/+packages)
have been using that for more than a year.
Now that we are at it: removing the "CONFIRMED" status since the same one that
opens a report can not be the one that confirms it, as we already know
(otherwise, all would be "CONFIRMED" bugs).
--
You are receiving this mail because:
You are watching all bug changes.
