https://bugs.kde.org/show_bug.cgi?id=447394
Toni Asensi Esteve <toni.ase...@kdemail.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|1 |0
Status|CONFIRMED |REPORTED
--- Comment #4 from Toni Asensi Esteve <toni.ase...@kdemail.net> ---
> New Tab actions perform a tab duplication [...] And there is definitely an
> inconsistency [...]
> there are two options "New Tab" and "Duplicate Current Tab", which do the
> same thing [...]
That is not true, "Duplicate tab" always opens the duplicated tab next to the
previous one, though with "new tab": that depends on the "Insert tabs after
current" ("Insert new tabs after current one") setting that the user can
choose. So the user can choose opening new tabs at the end of the row and still
duplicate a tab next to the original one (like in web browsers).
On
https://invent.kde.org/utilities/krusader/-/merge_requests?scope=all&state=merged
anyone can see the upvotes, for example to "New tabs start in the current
folder and can be inserted next to the current tab or at the end" . Developers
of Krusader can have accepted a merge request using the means they have
considered adequate in that moment ─like a comment, an upvote, etc. without
being told now to go back and do it again, this time looking for a tag, click a
link, etc.☹
Knowing that Konsole, Double Commander, Total Commander, Dolphin, (for more
than a year) people who use the git version of Krusader, users of the [PPA of
Rik
Mills](https://launchpad.net/~rikmills/+archive/ubuntu/experimental/+packages)
and other places that may exist like
https://aur.archlinux.org/packages/krusader-git use that way, someone would
think about a user study would be done to show that all that software is doing
it incorrectly.
Writing more now about that would be repeating what is already stated there and
in the merge request.
--
You are receiving this mail because:
You are watching all bug changes.
