https://bugs.kde.org/show_bug.cgi?id=426525
Bug ID: 426525
Summary: Key sequences ambiguous by default
Product: kdevelop
Version: 5.6.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: UI: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: pugach.yarosl...@gmail.com
Target Milestone: ---
Created attachment 131641
--> https://bugs.kde.org/attachment.cgi?id=131641&action=edit
Error message
SUMMARY
KDevelop AppImage reports a lot of ambiguous key sequences when installed as
is.
STEPS TO REPRODUCE
1. Follow the official guide to download and run KDevelop:
{{Output|1=<nowiki>
wget -O KDevelop.AppImage
https://download.kde.org/stable/kdevelop/5.6.0/bin/linux/KDevelop-5.6.0-x86_64.AppImage
chmod +x KDevelop.AppImage
./KDevelop.AppImage
</nowiki>}}
2. Open a project, set a breakpoint, and run debug launch.
3. Hit F10 to step over.
OBSERVED RESULT
The message pops up saying
<blockquote>
The key sequence 'F10' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.
</blockquote>
See the screenshot attached.
EXPECTED RESULT
The instruction pointer moving to the next code line.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Going to keyboard shortcut configuration and searching for F10 key proves that
the key is indeed ambiguous. By default it has been assigned to Dynamic Word
Wrap (Kate Part) and Step Over (Debugger). Sure, I can change the key, but
isn't it supposed to work right out of the box? Moreover, there are many other
keys which bring about the same issue.
--
You are receiving this mail because:
You are watching all bug changes.
