Bug 366075

Summary: Create New Folder shortcut F10 not indicated in the menu File->Create New
Product: [Frameworks and Libraries] frameworks-kio Reporter: Carsten <c.v.k>
Component: generalAssignee: David Faure <faure>
Status: RESOLVED FIXED    
Severity: minor CC: bugseforuns, elijah, elvis.angelaccio, kdelibs-bugs-null
Priority: NOR    
Version First Reported In: 5.24.0   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: http://commits.kde.org/kio/8d9befe7c9f7813352ddb4b6a1c169f31e5f5365 Version Fixed/Implemented In: 5.27
Sentry Crash Report:

Description Carsten 2016-07-25 09:24:55 UTC 
Despite using Dolphin since several years I only recently discovered that there is a shortcut for the creation of a new directory: F10.

I would have expected that all existing short cuts are written after the respective entry in the respective menu. For File->Create New->Folder This is not the case. (Maybe for other actions too?)

Since knowing the F10 shortcut, I like dolphin even more, so I think it is worth spreading.


Disclaimer: I am using Dolphin 4.14.2 which ships with debian stable, so maybe this is fixed already.

Reproducible: Always

Steps to Reproduce:
1. Open the menu: File
2. Hover the mouse over Create New -> Folder


Actual Results:  
Shortcut indication missing
Comment 1 Patrick Silva 2016-08-20 23:03:18 UTC 
Same ithing in dolphin 16.04.3 from Arch repositories.
Comment 2 Elvis Angelaccio 2016-08-25 16:58:30 UTC 
Moving to KIO. Patch in https://git.reviewboard.kde.org/r/128759/
Comment 3 Elvis Angelaccio 2016-09-07 07:05:39 UTC 
Git commit 8d9befe7c9f7813352ddb4b6a1c169f31e5f5365 by Elvis Angelaccio.
Committed on 07/09/2016 at 06:57.
Pushed by elvisangelaccio into branch 'master'.

KNewFileMenu: show New Folder action shortcut

REVIEW: 128759
FIXED-IN: 5.27

M  +13   -0    src/filewidgets/knewfilemenu.cpp
M  +3    -0    src/filewidgets/knewfilemenu.h

http://commits.kde.org/kio/8d9befe7c9f7813352ddb4b6a1c169f31e5f5365
Comment 4 Elvis Angelaccio 2016-12-10 11:26:55 UTC 
*** Bug 250317 has been marked as a duplicate of this bug. ***