Bug 347003 - Kile doesn't fetch the global standard keyboard shortcuts of KDE
Summary: Kile doesn't fetch the global standard keyboard shortcuts of KDE
Status: REPORTED
Alias: None
Product: kile
Classification: Applications
Component: user interface (show other bugs)
Version: 2.1.3
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-01 11:24 UTC by oncelacar
Modified: 2021-03-09 06:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description oncelacar 2015-05-01 11:24:01 UTC
I customize my standard keyboard shortcuts through KDE's System Settings winidow. While all the other KDE applications inherit the new standard shortcut combinations, Kile doesn't.

Reproducible: Always

Steps to Reproduce:
1. Open System Settings.
2. Modify the default keyboard shortcut function for a common command (let's say set "save" to Ctrl+E from the default value of Ctrl+S).
3. Open Kile and try to invoke the shortcut combination.

Actual Results:  
The newly set function of the shortcut combination is not executed.

Expected Results:  
If there are no shortcut conflicts/ambiguities, the function associated with the shortcut through the System Settings should be executed. If there is a conflict, Kile should detect this and show a popup warning, saying no action will be triggered.

Reported for Debian 8.0, but I have observed this with Kile all along in earlier versions too.
Comment 1 oncelacar 2015-05-01 13:10:33 UTC
Update: I just noticed that Kile has indeed inherited the shortcut combination for "open", "save as" and "print". The problem remains though, for "save", "select all", "undo", "redo" and possibly several others. I am afraid it might be necessary to check the behaviour for all shortcut functions.
Comment 2 Justin Zobel 2021-03-09 06:59:13 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.