Bug 30864 - Can't type ">" in kate as it appears to be internally associated with a GUI shortcut that is not settable in the config
Summary: Can't type ">" in kate as it appears to be internally associated with a GUI s...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-19 00:05 CEST by Barry Jackson
Modified: 2022-09-20 00:26 CEST (History)
1 user (show)

See Also:
Source RPM: kate-22.08.1-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Barry Jackson 2022-09-19 00:05:18 CEST
Description of problem:
All in the summary.

kwrite works as expected.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2022-09-19 21:21:54 CEST
I just installed kate-22.08.1-1.mga9.x86_64.rpm to try to reproduce this issue, but typing ">" works fine for me.
I also tried with Kate started in en_GB

Anyway assigning to the KDE maintainers, I assume there are more users with such internal shortcut.

Btw, does it happen to a new user, if you create one, too?

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 2 Barry Jackson 2022-09-20 00:26:10 CEST
(In reply to Marja Van Waes from comment #1)
> I just installed kate-22.08.1-1.mga9.x86_64.rpm to try to reproduce this
> issue, but typing ">" works fine for me.
> I also tried with Kate started in en_GB
> 
> Anyway assigning to the KDE maintainers, I assume there are more users with
> such internal shortcut.
> 
> Btw, does it happen to a new user, if you create one, too?

Thanks Marja,
I just spent another half hour searching through all the references to kate in my ~/ and then decided to have another look in the settings, after checking in another user that I could type >.

I found it, by searching the keyboard shortcuts dialogue for > and it was set (very hidden) to add a tab for something above the text window. I can't even find the feature now and I have no clue how it became set - certainly was not by me!

Sorry for the noise, at least this may solve it for others if they hit the same issue :)

Closing as invalid.

Resolution: (none) => INVALID
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.