| Summary: | Ambiguous shortcut warning shown on launch | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Nate Graham <nate> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | christoph, marci, waqar.17a |
| Priority: | NOR | Keywords: | regression |
| Version First Reported In: | Git | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Ambiguous shortcut warning
Only one thing in Kate using it |
||
I was not able to reproduce after updating to the latest. We recently moved the "Diagnostics" stuff to a more global level in Kate which includes this "QuickFix" action with the shortcut (Ctrl + Key_Period). Previously this action was in LSP plugin with the same shortcut. Could it be that you have the `Ctrl+.` manually configured to something else? The default shortcut for "Next Tab" should be `Alt + Right` Created attachment 155261 [details]
Only one thing in Kate using it
Nope, only Quick Fix is using Ctrl+. in Kate.
So this means that either the other usage of the Ctrl+. shortcut comes from something in frameworks, or there's a bug that was introduced recently, probably in KStandardShortcut. This message started appearing for me as well around 1-2 weeks ago after an update, not sure which version. I checked shortcuts under System Settings, and I had custom shortcuts for Ctrl+. and Ctrl+, for "activate next/previous tab". I don't recall adding these myself, maybe they are some old default? My installation is around 5 years old. In any case, I removed those and the message no longer appears. I'm on OpenSUSE Tumbleweed, currently on KDE 5.27.5, frameworks 5.106.0. Can not reproduce that with Kate 23.08 or later. |
Created attachment 155238 [details] Ambiguous shortcut warning Today's git master of all KDE repos shows me an ambiguous shortcut warning (see attachment) when I launch Kate. It does not happen when I launch KWrite.