Bug 435318

Summary:	Allow using the "²" (square) key as the compose key
Product:	[Applications] systemsettings	Reporter:	Raphaël Jakse <raphael.kde>
Component:	kcm_keyboard	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	wishlist	CC:	butirsky
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
URL:	https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/264
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Raphaël Jakse 2021-04-03 18:45:51 UTC

SUMMARY

I never use the ² key. All the keys that can be configured as the Compose key are either awkward combinations like AltGr+Menu, or keys that are useful for shortcuts / used in default shortcuts (Meta) or for window actions (alt + move).

Be able to configure from the "²" key as a Compose key from the GUI would be neat. I can afford to type Circonflex + 2 to type ², I have to do it for ¹ or ³ anyway.

Let's make this key eventually useful! :-) 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: on openSUSE Tumbleweed
KDE Plasma Version: 5.21.3 
KDE Frameworks Version:  5.80.0
Qt Version: 5.15.12

Comment 1 Andrey 2021-04-03 18:54:09 UTC

That probably should go to https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues?
Because what we display in Keyboard Advanced Options tab come from there.

Comment 2 Raphaël Jakse 2021-04-03 21:14:37 UTC

Thanks for the directions. I didn't find a ticket about it there so I opened a new one: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/264

Comment 3 Raphaël Jakse 2021-04-06 05:42:44 UTC

My bug there has been closed with the suggestion to use a local custom configuration for this, so I guess we won't see "²" as a possible option for the compose key in the GUI by default anytime soon.

Comment 4 Andrey 2021-04-06 18:14:26 UTC

Did you try the suggestion proposed upstream?

Comment 5 Raphaël Jakse 2021-04-06 18:23:52 UTC

No. I just read the blog article Peter linked, and then some more out of curiosity and interest.

I could fix it for myself, but was aiming for a solution that would make easy-to-use for everyone. But a custom manual XML configuration won't cut it.

I'm less motivated by a solution that works only for me. I'll apply it when I'll eventually reach a point when I'm fed up with my setup. This could happen tomorrow or in a month. But I don't want to have to tell people "Hey, there's this cool feature that allows you to write useful and fun characters easily, and you can take advantage of this key that you never used in your life for that, only you need to write this XML stuff, trust me it is easy".

However, if me trying this could potentially lead to a solution for all users, or at least KDE users (if, for instance, the KDE project is willing to ship such custom configuration - even in an optional package), I'll gladly look into it before reaching the fed up point :-)

Comment 6 Raphaël Jakse 2021-04-06 18:28:21 UTC

Actually, this makes me think the I could probably package something on my own, this is not specific to KDE after all. Even better if KDE ships it by default so if you are interested, let me know and I'll look into it when I find the time.

Comment 7 Andrey 2021-04-06 18:52:33 UTC

I recommend you try it and when you end up with fine grained option which looks nice and doesn't interfere with the others, you could make a MR upstream so it could be reconsidered.  
Anyway, I think it has nothing to do with KDE.

Comment 8 Raphaël Jakse 2021-04-06 18:54:44 UTC

You are right. Thank your for your help!